CVE-2026-53265
Vulnerability Scoring
Analysis In Progress
CVE-2026-53265 Vulnerability Analysis & Exploit Details
CVE-2026-53265
Attack Complexity Details
-
Attack Complexity:
Attack Complexity Analysis In Progress
-
Attack Vector:
Attack Vector Under Analysis
-
Privileges Required:
None
No authentication is required for exploitation.
-
Scope:
Impact is confined to the initially vulnerable component.
-
User Interaction:
None
No user interaction is necessary for exploitation.
CVE-2026-53265 Details
Status: Received on 25 Jun 2026, 09:16 UTC
Published on: 25 Jun 2026, 09:16 UTC
CVSS Release:
CVE-2026-53265 Vulnerability Summary
CVE-2026-53265: 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.
Assessing the Risk of CVE-2026-53265
Access Complexity Graph
The exploitability of CVE-2026-53265 depends on two key factors: attack complexity (the level of effort required to execute an exploit) and privileges required (the access level an attacker needs).
Exploitability Analysis for CVE-2026-53265
No exploitability data is available for CVE-2026-53265.
Understanding AC and PR
A lower complexity and fewer privilege requirements make exploitation easier. Security teams should evaluate these aspects to determine the urgency of mitigation strategies, such as patch management and access control policies.
Attack Complexity (AC) measures the difficulty in executing an exploit. A high AC means that specific conditions must be met, making an attack more challenging, while a low AC means the vulnerability can be exploited with minimal effort.
Privileges Required (PR) determine the level of system access necessary for an attack. Vulnerabilities requiring no privileges are more accessible to attackers, whereas high privilege requirements limit exploitation to authorized users with elevated access.
CVSS Score Breakdown Chart
Above is the CVSS Sub-score Breakdown for CVE-2026-53265, illustrating how Base, Impact, and Exploitability factors combine to form the overall severity rating. A higher sub-score typically indicates a more severe or easier-to-exploit vulnerability.
CIA Impact Analysis
Below is the Impact Analysis for CVE-2026-53265, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.
-
Confidentiality:
None
CVE-2026-53265 does not compromise confidentiality.
-
Integrity:
None
CVE-2026-53265 does not impact data integrity.
-
Availability:
None
CVE-2026-53265 does not affect system availability.
CVE-2026-53265 References
External References
- https://git.kernel.org/stable/c/03ffe1112ed88bb3a9bd0b971549bf4d64bfc59a
- https://git.kernel.org/stable/c/13da856c86fb8c2ccab95034fd77da1bb2c2a17c
- https://git.kernel.org/stable/c/42ff6774ecd9d7f70d599cb71ff64373a1da4948
- https://git.kernel.org/stable/c/b4892561552d671bd8c4da5ebb70e9fbb1ec446e
- https://git.kernel.org/stable/c/c242c7af2aecf0b538b8623bdb86b8b441da38d9
- https://git.kernel.org/stable/c/c57570fba24016ec25ec046ab44db39143fb7a64
- https://git.kernel.org/stable/c/d3f0a606b9f278ece8a0df626ded9c4044071235
- https://git.kernel.org/stable/c/d886945fcb0f8c9dc6b39928d7a96c95c587346c
CWE Common Weakness Enumeration
Unknown
Protect Your Infrastructure against CVE-2026-53265: Combat Critical CVE Threats
Stay updated with real-time CVE vulnerabilities and take action to secure your systems. Enhance your cybersecurity posture with the latest threat intelligence and mitigation techniques. Develop the skills necessary to defend against CVEs and secure critical infrastructures. Join the top cybersecurity professionals safeguarding today's infrastructures.
Other 5 Recently Published CVEs Vulnerabilities
- CVE-2026-56130 – "Remember me" cookie age is not verified on the server. This potentially allows an attacker to intercept a valid cookie and reuse it indefinitely, ...
- CVE-2026-56091 – When using Apache Shiro with the shiro-guice module in a web servlet context, a specially crafted HTTP request may cause an authentication bypass. ...
- CVE-2026-54226 – A vulnerability in Apache Kvrocks. This issue affects Apache Kvrocks: from 2.6.0 through 2.15.0. Users are recommended to upgrade to version 2.16...
- CVE-2026-53277 – In the Linux kernel, the following vulnerability has been resolved: KVM: arm64: Take the SRCU lock for page table walks in fault injection and AT ...
- CVE-2026-53276 – In the Linux kernel, the following vulnerability has been resolved: Bluetooth: ISO: Fix a use-after-free of the hci_conn pointer In iso_sock_rebi...