CVE-2023-53810
Vulnerability Scoring
Analysis In Progress
CVE-2023-53810 Vulnerability Analysis & Exploit Details
CVE-2023-53810
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-2023-53810 Details
Status: Received on 09 Dec 2025, 01:16 UTC
Published on: 09 Dec 2025, 01:16 UTC
CVSS Release:
CVE-2023-53810 Vulnerability Summary
CVE-2023-53810: In the Linux kernel, the following vulnerability has been resolved: blk-mq: release crypto keyslot before reporting I/O complete Once all I/O using a blk_crypto_key has completed, filesystems can call blk_crypto_evict_key(). However, the block layer currently doesn't call blk_crypto_put_keyslot() until the request is being freed, which happens after upper layers have been told (via bio_endio()) the I/O has completed. This causes a race condition where blk_crypto_evict_key() can see 'slot_refs != 0' without there being an actual bug. This makes __blk_crypto_evict_key() hit the 'WARN_ON_ONCE(atomic_read(&slot->slot_refs) != 0)' and return without doing anything, eventually causing a use-after-free in blk_crypto_reprogram_all_keys(). (This is a very rare bug and has only been seen when per-file keys are being used with fscrypt.) There are two options to fix this: either release the keyslot before bio_endio() is called on the request's last bio, or make __blk_crypto_evict_key() ignore slot_refs. Let's go with the first solution, since it preserves the ability to report bugs (via WARN_ON_ONCE) where a key is evicted while still in-use.
Assessing the Risk of CVE-2023-53810
Access Complexity Graph
The exploitability of CVE-2023-53810 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-2023-53810
No exploitability data is available for CVE-2023-53810.
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-2023-53810, 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-2023-53810, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.
-
Confidentiality:
None
CVE-2023-53810 does not compromise confidentiality.
-
Integrity:
None
CVE-2023-53810 does not impact data integrity.
-
Availability:
None
CVE-2023-53810 does not affect system availability.
CVE-2023-53810 References
External References
- https://git.kernel.org/stable/c/7d206ec7a04e8545828191b6ea8b49d3ea61391f
- https://git.kernel.org/stable/c/874bdf43b4a7dc5463c31508f62b3e42eb237b08
- https://git.kernel.org/stable/c/92d5d233b9ff531cf9cc36ab4251779e07adb633
- https://git.kernel.org/stable/c/9cd1e566676bbcb8a126acd921e4e194e6339603
- https://git.kernel.org/stable/c/b278570e2c59d538216f8b656e97680188a8fba4
- https://git.kernel.org/stable/c/d206f79d9cd658665b37ce8134c6ec849ac7af0c
CWE Common Weakness Enumeration
Unknown
Protect Your Infrastructure against CVE-2023-53810: 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-2025-66491 – Traefik is an HTTP reverse proxy and load balancer. Versions 3.5.0 through 3.6.2 have inverted TLS verification logic in the nginx.ingress.kubernet...
- CVE-2025-66490 – Traefik is an HTTP reverse proxy and load balancer. For versions prior to 2.11.32 and 2.11.31 through 3.6.2, requests using PathPrefix, Path or Pat...
- CVE-2025-66481 – DeepChat is an open-source AI chat platform that supports cloud models and LLMs. Versions 0.5.1 and below are vulnerable to XSS attacks through imp...
- CVE-2025-66470 – NiceGUI is a Python-based UI framework. Versions 3.3.1 and below are subject to a XSS vulnerability through the ui.interactive_image component of N...
- CVE-2025-14285 – A vulnerability was found in code-projects Employee Profile Management System 1.0. Affected is an unknown function of the file edit_personnel.php. ...