Menu

Star on GitHub · 3.2k

CVE-2026-53265

7.8 · HIGH

In the Linux kernel, the following vulnerability has been resolved: dm cache policy smq: check allocation under invalidate lock commit 2d1f7b65f5de ("dm cache policy smq: fix missing locks in inv…

Published Jun 25, 2026EPSS 0.12%

Overview

CVE-2026-53265 is a high-severity vulnerability. It was published on June 25, 2026 and has a CVSS 3.1 base score of 7.8 (HIGH).

This vulnerability has a CVSS 3.1 base score of 7.8, rated HIGH. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

Technical description

In the Linux kernel, the following vulnerability has been resolved:

dm cache policy smq: check allocation under invalidate lock

commit 2d1f7b65f5de ("dm cache policy smq: fix missing locks in

invalidating cache blocks") added mq->lock around the destructive part of

smq_invalidate_mapping(), but left the e->allocated check outside the

critical section.

That leaves a check-then-act race. Two concurrent invalidators can both

observe e->allocated as true before either of them takes mq->lock. The

first invalidator that acquires the lock removes the entry from the

queues and hash table and then calls free_entry(), which clears

e->allocated and puts the entry back on the free list. The second

invalidator can then acquire mq->lock and continue with the stale result

of the unlocked check.

This can corrupt the SMQ queues or hash table by deleting an entry that

is no longer on those structures. It can also hit the allocation check in

free_entry() when the same entry is freed again.

Move the

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2026-53265?

CVE-2026-53265 is a high-severity vulnerability. It was published on June 25, 2026 and has a CVSS 3.1 base score of 7.8 (HIGH).

How severe is CVE-2026-53265?

This vulnerability has a CVSS 3.1 base score of 7.8, rated HIGH. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

How do I fix or remediate CVE-2026-53265?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2026-53265?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2026-53265 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related HIGH CVEs from 2026

View all