CVE-2026-53265
Last modified
CVE-2026-53265 is a high-severity vulnerability rated 7.8/10 on the CVSS scale. 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. EPSS estimates a 0.13% chance of exploitation in the next 30 days.
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 allocation check under mq->lock so the predicate and the destructive operations are serialized by the same lock.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Linux | Linux Kernel | >= 6.6.141, < 6.6.143 | — |
| Linux | Linux Kernel | >= 6.12.91, < 6.12.94 | — |
| Linux | Linux Kernel | >= 6.18.33, < 6.18.36 | — |
| Linux | Linux Kernel | >= 7.0.10, < 7.0.13 | — |
| Linux | Linux Kernel | 5.10.258 | — |
| Linux | Linux Kernel | 5.15.209 | — |
| Linux | Linux Kernel | 6.1.175 | — |
| Linux | Linux Kernel | 7.1 | Rc1 |
References
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2026-53265?
How severe is CVE-2026-53265?
How do I fix CVE-2026-53265?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-5326A vulnerability was identified in SourceCodester Leave Appli…5.5
- CVE-2026-53260In the Linux kernel, the following vulnerability has been re…9.8
- CVE-2026-53261In the Linux kernel, the following vulnerability has been re…
- CVE-2026-53262In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-53263In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-53264In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-53266In the Linux kernel, the following vulnerability has been re…8.8
- CVE-2026-53267In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-53268In the Linux kernel, the following vulnerability has been re…8.2
- CVE-2026-53269In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-5327A security flaw has been discovered in efforthye fast-filesy…6.3
- CVE-2026-53270In the Linux kernel, the following vulnerability has been re…7.8
Are you affected by CVE-2026-53265?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
