Answer in brief
CVE-2026-53265 records a High severity (CVSS 7.8) vulnerability in dm cache policy smq: check allocation under invalidate lock. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
Answer in brief
CVE-2026-53265 records a High severity (CVSS 7.8) vulnerability in dm cache policy smq: check allocation under invalidate lock. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=4991b5a08751e2e82488fb93ae08849b6aea10d9 <c242c7af2aecf0b538b8623bdb86b8b441da38d9 || >=1b2bec4a7dcf5f00b7a1cbeeec8997841d783513 <13da856c86fb8c2ccab95034fd77da1bb2c2a17c || >=9a5fdfb9e57ec3a8ad2b8fce5e5ffa42d53b130e <d886945fcb0f8c9dc6b39928d7a96c95c587346c || >=ac5ee99443891bdb161f5539606a66a1b5e72542 <b4892561552d671bd8c4da5ebb70e9fbb1ec446e || >=93627a29d4b66d4a2def938dfb8610cc80ae454b <03ffe1112ed88bb3a9bd0b971549bf4d64bfc59a || >=c348ae47d8e65f06429fa41adce9ad986b696766 <42ff6774ecd9d7f70d599cb71ff64373a1da4948 || >=2b62d0611c9af14a16bddf22df2612b4f40eb5a1 <c57570fba24016ec25ec046ab44db39143fb7a64 || >=2d1f7b65f5deedd2e6b09fdc6ea27f8375f24b45 <d3f0a606b9f278ece8a0df626ded9c4044071235 | c242c7af2aecf0b538b8623bdb86b8b441da38d9, 13da856c86fb8c2ccab95034fd77da1bb2c2a17c, d886945fcb0f8c9dc6b39928d7a96c95c587346c, b4892561552d671bd8c4da5ebb70e9fbb1ec446e, 03ffe1112ed88bb3a9bd0b971549bf4d64bfc59a, 42ff6774ecd9d7f70d599cb71ff64373a1da4948, c57570fba24016ec25ec046ab44db39143fb7a64, d3f0a606b9f278ece8a0df626ded9c4044071235 |
| Linux/Linuxgeneric | >=5.10.258 <5.10.259 || >=5.15.209 <5.15.210 || >=6.1.175 <6.1.176 || >=6.6.141 <6.6.143 || >=6.12.91 <6.12.94 || >=6.18.33 <6.18.36 || >=7.0.10 <7.0.13 | 5.10.259, 5.15.210, 6.1.176, 6.6.143, 6.12.94, 6.18.36, 7.0.13 |
Published upstream
Jun 25, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jun 25, 2026
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.
Quoted source text, attributed separately from HOL analysis.
CVSS is 7.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=4991b5a08751e2e82488fb93ae08849b6aea10d9 <c242c7af2aecf0b538b8623bdb86b8b441da38d9 || >=1b2bec4a7dcf5f00b7a1cbeeec8997841d783513 <13da856c86fb8c2ccab95034fd77da1bb2c2a17c || >=9a5fdfb9e57ec3a8ad2b8fce5e5ffa42d53b130e <d886945fcb0f8c9dc6b39928d7a96c95c587346c || >=ac5ee99443891bdb161f5539606a66a1b5e72542 <b4892561552d671bd8c4da5ebb70e9fbb1ec446e || >=93627a29d4b66d4a2def938dfb8610cc80ae454b <03ffe1112ed88bb3a9bd0b971549bf4d64bfc59a || >=c348ae47d8e65f06429fa41adce9ad986b696766 <42ff6774ecd9d7f70d599cb71ff64373a1da4948 || >=2b62d0611c9af14a16bddf22df2612b4f40eb5a1 <c57570fba24016ec25ec046ab44db39143fb7a64 || >=2d1f7b65f5deedd2e6b09fdc6ea27f8375f24b45 <d3f0a606b9f278ece8a0df626ded9c4044071235 | c242c7af2aecf0b538b8623bdb86b8b441da38d9, 13da856c86fb8c2ccab95034fd77da1bb2c2a17c, d886945fcb0f8c9dc6b39928d7a96c95c587346c, b4892561552d671bd8c4da5ebb70e9fbb1ec446e, 03ffe1112ed88bb3a9bd0b971549bf4d64bfc59a, 42ff6774ecd9d7f70d599cb71ff64373a1da4948, c57570fba24016ec25ec046ab44db39143fb7a64, d3f0a606b9f278ece8a0df626ded9c4044071235 |
| Linux/Linuxgeneric | >=5.10.258 <5.10.259 || >=5.15.209 <5.15.210 || >=6.1.175 <6.1.176 || >=6.6.141 <6.6.143 || >=6.12.91 <6.12.94 || >=6.18.33 <6.18.36 || >=7.0.10 <7.0.13 | 5.10.259, 5.15.210, 6.1.176, 6.6.143, 6.12.94, 6.18.36, 7.0.13 |
Published upstream
Jun 25, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jun 25, 2026
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.
Quoted source text, attributed separately from HOL analysis.