CVE-2026-53265

dm cache policy smq: check allocation under invalidate lock

HIGH
7.8
CVSS Score
Published: June 25, 2026 at 08:39 AM UTC
Updated: October 19, 2026 at 08:19 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.8
Exploit prediction
EPSS 0.1%
SSVC
No known exploit

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

6.12.91 ≤ v < 6.12.946.18.33 ≤ v < 6.18.366.6.141 ≤ v < 6.6.1437.0.10 ≤ v < 7.0.131b2bec4a7dcf5f00b7a1cbeeec8997841d7835132b62d0611c9af14a16bddf22df2612b4f40eb5a12d1f7b65f5deedd2e6b09fdc6ea27f8375f24b454991b5a08751e2e82488fb93ae08849b6aea10d95.10.2585.15.2096.1.1756.12.916.18.336.6.1417.0.107.17.1 rc17.1 rc27.1 rc37.1 rc47.1 rc57.1 rc693627a29d4b66d4a2def938dfb8610cc80ae454b9a5fdfb9e57ec3a8ad2b8fce5e5ffa42d53b130eac5ee99443891bdb161f5539606a66a1b5e72542c348ae47d8e65f06429fa41adce9ad986b696766
Vendor states this is fixed in 03ffe1112ed88bb3a9bd0b971549bf4d64bfc59a (fixed)
Vendor states this is fixed in 13da856c86fb8c2ccab95034fd77da1bb2c2a17c (fixed)
Vendor states this is fixed in 42ff6774ecd9d7f70d599cb71ff64373a1da4948 (fixed)
Vendor states this is fixed in b4892561552d671bd8c4da5ebb70e9fbb1ec446e (fixed)
Vendor states this is fixed in c242c7af2aecf0b538b8623bdb86b8b441da38d9 (fixed)
Vendor states this is fixed in c57570fba24016ec25ec046ab44db39143fb7a64 (fixed)
Vendor states this is fixed in d3f0a606b9f278ece8a0df626ded9c4044071235 (fixed)
Vendor states this is fixed in d886945fcb0f8c9dc6b39928d7a96c95c587346c (fixed)
Affected range stops below 5.10.259, so it looks safe — our inference, not a vendor statement
Affected range stops below 5.15.210, so it looks safe — our inference, not a vendor statement
Affected range stops below 6.1.176, so it looks safe — our inference, not a vendor statement
Affected range stops below 6.12.94, so it looks safe — our inference, not a vendor statement
Affected range stops below 6.18.36, so it looks safe — our inference, not a vendor statement
Affected range stops below 6.6.143, so it looks safe — our inference, not a vendor statement
Affected range stops below 7.0.13, so it looks safe — our inference, not a vendor statement

SSVC — Action Prioritization

SSVCNo known exploitNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

7.8HIGHLinux
Vector?

Quick Info

StatusMODIFIED
CWE
NVD-CWE-noinfoCWE-362

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card