CVE-2023-53536 Details
Description
In the Linux kernel, the following vulnerability has been resolved: blk-crypto: make blk_crypto_evict_key() more robust If blk_crypto_evict_key() sees that the key is still in-use (due to a bug) or that ->keyslot_evict failed, it currently just returns while leaving the key linked into the keyslot management structures. However, blk_crypto_evict_key() is only called in contexts such as inode eviction where failure is not an option. So actually the caller proceeds with freeing the blk_crypto_key regardless of the return value of blk_crypto_evict_key(). These two assumptions don't match, and the result is that there can be a use-after-free in blk_crypto_reprogram_all_keys() after one of these errors occurs. (Note, these errors *shouldn't* happen; we're just talking about what happens if they do anyway.) Fix this by making blk_crypto_evict_key() unlink the key from the keyslot management structures even on failure. Also improve some comments.
A vulnerability in the Linux kernel's block crypto key management can cause a use-after-free error. This issue arises in the blk_crypto_evict_key() function, which is responsible for evicting encryption keys from hardware. If the function detects that a key is still in use or fails to evict it from a keyslot, it currently returns without unlinking the key from the management structures. This behavior creates a mismatch, as the function is called in contexts where failure is not acceptable, leading to potential memory management errors.
Users can upgrade to the latest version of the Linux kernel where this vulnerability has been addressed.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
No SSVC data is available for this CVE.
References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://git.kernel.org/stable/c/5bb4005fb667c6e2188fa87950f8d5faf2994410 | kernel.org | Patch |
| https://git.kernel.org/stable/c/5c62852942667c613de0458fc797c5b8c36112b5 | kernel.org | Patch |
| https://git.kernel.org/stable/c/5c7cb94452901a93e90c2230632e2c12a681bc92 | kernel.org | Patch |
| https://git.kernel.org/stable/c/64ef787bb1588475163069c2e62fdd8f6c27b1f6 | kernel.org | Patch |
| https://git.kernel.org/stable/c/701a8220762ff90615dc91d3543f789391b63298 | kernel.org | Patch |
| https://git.kernel.org/stable/c/809a5be62e92a444a3c3d7b9f438019d0b322f55 | kernel.org | Patch |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-416 | Use After Free | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| linux linux kernel | >= 5.8, < 5.10.180 >= 5.11, < 5.15.111 >= 5.16, < 6.1.28 >= 6.2, < 6.2.15 >= 6.3, < 6.3.2 |
CPE
Remediation
| |
Change History
5 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Aug 4, 2026 | CVE Modified | kernel.org |
| Jun 17, 2026 | CVE Modified | kernel.org |
| Mar 25, 2026 | Modified Analysis | [email protected] |
| Feb 9, 2026 | Initial Analysis | [email protected] |
| Oct 4, 2025 | New CVE Received | kernel.org |