CVE-2026-53265

published 25 Jun 2026 · updated 19 Oct 2026

dm cache policy smq: check allocation under invalidate lock

7.8HighCVSS 7.8EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 13da856c86fb8c2ccab95034fd77da1bb2c2a17c, Kernel c57570fba24016ec25ec046ab44db39143fb7a64, Kernel d3f0a606b9f278ece8a0df626ded9c4044071235 and 12 more.

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

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel>=1b2bec4a7dcf5f00b7a1cbeeec8997841d783513 <13da856c86fb8c2ccab95034fd77da1bb2c2a17c, >=2b62d0611c9af14a16bddf22df2612b4f40eb5a1 <c57570fba24016ec25ec046ab44db39143fb7a64, >=2d1f7b65f5deedd2e6b09fdc6ea27f8375f24b45 <d3f0a606b9f278ece8a0df626ded9c4044071235, >=4991b5a08751e2e82488fb93ae08849b6aea10d9 <c242c7af2aecf0b538b8623bdb86b8b441da38d9, >=5.10.258 <5.10.259, >=5.15.209 <5.15.210, >=6.1.175 <6.1.176, >=6.12.91 <6.12.94, >=6.18.33 <6.18.36, >=6.6.141 <6.6.143, >=7.0.10 <7.0.13, >=93627a29d4b66d4a2def938dfb8610cc80ae454b <03ffe1112ed88bb3a9bd0b971549bf4d64bfc59a, >=9a5fdfb9e57ec3a8ad2b8fce5e5ffa42d53b130e <d886945fcb0f8c9dc6b39928d7a96c95c587346c, >=ac5ee99443891bdb161f5539606a66a1b5e72542 <b4892561552d671bd8c4da5ebb70e9fbb1ec446e, >=c348ae47d8e65f06429fa41adce9ad986b696766 <42ff6774ecd9d7f70d599cb71ff64373a1da494813da856c86fb8c2ccab95034fd77da1bb2c2a17c, c57570fba24016ec25ec046ab44db39143fb7a64, d3f0a606b9f278ece8a0df626ded9c4044071235, c242c7af2aecf0b538b8623bdb86b8b441da38d9, 5.10.259, 5.15.210, 6.1.176, 6.12.94, 6.18.36, 6.6.143, 7.0.13, 03ffe1112ed88bb3a9bd0b971549bf4d64bfc59a, d886945fcb0f8c9dc6b39928d7a96c95c587346c, b4892561552d671bd8c4da5ebb70e9fbb1ec446e, 42ff6774ecd9d7f70d599cb71ff64373a1da4948

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-53265 severity on Zeptric[![CVE-2026-53265](https://zeptric.io/badge/cve/CVE-2026-53265.svg)](https://zeptric.io/cve/CVE-2026-53265)