CVE-2026-53265
dm cache policy smq: check allocation under invalidate lock
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.
INFO
Published Date :
June 25, 2026, 9:16 a.m.
Last Modified :
July 8, 2026, 4:02 a.m.
Remotely Exploit :
No
Source :
416baaa9-dc9f-4396-8d5f-8c081fb06d67
CVSS Scores
| Score | Version | Severity | Vector | Exploitability Score | Impact Score | Source |
|---|---|---|---|---|---|---|
| CVSS 3.1 | HIGH | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
Solution
- Move the allocation check under the invalidate lock.
- Ensure predicate and destructive operations are serialized by the same lock.
- Review related locking mechanisms for consistency.
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2026-53265.
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2026-53265 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2026-53265
weaknesses.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2026-53265 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2026-53265 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
Initial Analysis by [email protected]
Jul. 08, 2026
Action Type Old Value New Value Added CWE NVD-CWE-noinfo Added CPE Configuration OR *cpe:2.3:o:linux:linux_kernel:7.1:rc1:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:7.1:rc2:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:7.1:rc3:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:7.1:rc4:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:7.1:rc5:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:7.1:rc6:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 7.0.10 up to (excluding) 7.0.13 *cpe:2.3:o:linux:linux_kernel:5.15.209:*:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.12.91 up to (excluding) 6.12.94 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.18.33 up to (excluding) 6.18.36 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.6.141 up to (excluding) 6.6.143 *cpe:2.3:o:linux:linux_kernel:5.10.258:*:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:6.1.175:*:*:*:*:*:*:* Added Reference Type kernel.org: https://git.kernel.org/stable/c/03ffe1112ed88bb3a9bd0b971549bf4d64bfc59a Types: Patch Added Reference Type kernel.org: https://git.kernel.org/stable/c/13da856c86fb8c2ccab95034fd77da1bb2c2a17c Types: Patch Added Reference Type kernel.org: https://git.kernel.org/stable/c/42ff6774ecd9d7f70d599cb71ff64373a1da4948 Types: Patch Added Reference Type kernel.org: https://git.kernel.org/stable/c/b4892561552d671bd8c4da5ebb70e9fbb1ec446e Types: Patch Added Reference Type kernel.org: https://git.kernel.org/stable/c/c242c7af2aecf0b538b8623bdb86b8b441da38d9 Types: Patch Added Reference Type kernel.org: https://git.kernel.org/stable/c/c57570fba24016ec25ec046ab44db39143fb7a64 Types: Patch Added Reference Type kernel.org: https://git.kernel.org/stable/c/d3f0a606b9f278ece8a0df626ded9c4044071235 Types: Patch Added Reference Type kernel.org: https://git.kernel.org/stable/c/d886945fcb0f8c9dc6b39928d7a96c95c587346c Types: Patch -
CVE Modified by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Jun. 28, 2026
Action Type Old Value New Value Added CVSS V3.1 AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H -
New CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Jun. 25, 2026
Action Type Old Value New Value Added Affected [{'repo': 'https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git', 'vendor': 'Linux', 'product': 'Linux', 'versions': [{'status': 'affected', 'version': '4991b5a08751e2e82488fb93ae08849b6aea10d9', 'lessThan': 'c242c7af2aecf0b538b8623bdb86b8b441da38d9', 'versionType': 'git'}, {'status': 'affected', 'version': '1b2bec4a7dcf5f00b7a1cbeeec8997841d783513', 'lessThan': '13da856c86fb8c2ccab95034fd77da1bb2c2a17c', 'versionType': 'git'}, {'status': 'affected', 'version': '9a5fdfb9e57ec3a8ad2b8fce5e5ffa42d53b130e', 'lessThan': 'd886945fcb0f8c9dc6b39928d7a96c95c587346c', 'versionType': 'git'}, {'status': 'affected', 'version': 'ac5ee99443891bdb161f5539606a66a1b5e72542', 'lessThan': 'b4892561552d671bd8c4da5ebb70e9fbb1ec446e', 'versionType': 'git'}, {'status': 'affected', 'version': '93627a29d4b66d4a2def938dfb8610cc80ae454b', 'lessThan': '03ffe1112ed88bb3a9bd0b971549bf4d64bfc59a', 'versionType': 'git'}, {'status': 'affected', 'version': 'c348ae47d8e65f06429fa41adce9ad986b696766', 'lessThan': '42ff6774ecd9d7f70d599cb71ff64373a1da4948', 'versionType': 'git'}, {'status': 'affected', 'version': '2b62d0611c9af14a16bddf22df2612b4f40eb5a1', 'lessThan': 'c57570fba24016ec25ec046ab44db39143fb7a64', 'versionType': 'git'}, {'status': 'affected', 'version': '2d1f7b65f5deedd2e6b09fdc6ea27f8375f24b45', 'lessThan': 'd3f0a606b9f278ece8a0df626ded9c4044071235', 'versionType': 'git'}], 'programFiles': ['drivers/md/dm-cache-policy-smq.c'], 'defaultStatus': 'unaffected'}, {'repo': 'https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git', 'vendor': 'Linux', 'product': 'Linux', 'versions': [{'status': 'affected', 'version': '5.10.258', 'lessThan': '5.10.259', 'versionType': 'semver'}, {'status': 'affected', 'version': '5.15.209', 'lessThan': '5.15.210', 'versionType': 'semver'}, {'status': 'affected', 'version': '6.1.175', 'lessThan': '6.1.176', 'versionType': 'semver'}, {'status': 'affected', 'version': '6.6.141', 'lessThan': '6.6.143', 'versionType': 'semver'}, {'status': 'affected', 'version': '6.12.91', 'lessThan': '6.12.94', 'versionType': 'semver'}, {'status': 'affected', 'version': '6.18.33', 'lessThan': '6.18.36', 'versionType': 'semver'}, {'status': 'affected', 'version': '7.0.10', 'lessThan': '7.0.13', 'versionType': 'semver'}], 'programFiles': ['drivers/md/dm-cache-policy-smq.c'], 'defaultStatus': 'unaffected'}] Added 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. Added Reference https://git.kernel.org/stable/c/03ffe1112ed88bb3a9bd0b971549bf4d64bfc59a Added Reference https://git.kernel.org/stable/c/13da856c86fb8c2ccab95034fd77da1bb2c2a17c Added Reference https://git.kernel.org/stable/c/42ff6774ecd9d7f70d599cb71ff64373a1da4948 Added Reference https://git.kernel.org/stable/c/b4892561552d671bd8c4da5ebb70e9fbb1ec446e Added Reference https://git.kernel.org/stable/c/c242c7af2aecf0b538b8623bdb86b8b441da38d9 Added Reference https://git.kernel.org/stable/c/c57570fba24016ec25ec046ab44db39143fb7a64 Added Reference https://git.kernel.org/stable/c/d3f0a606b9f278ece8a0df626ded9c4044071235 Added Reference https://git.kernel.org/stable/c/d886945fcb0f8c9dc6b39928d7a96c95c587346c