blk-crypto: make blk_crypto_evict_key() more robust
Summary
| CVE | CVE-2023-53536 |
|---|---|
| State | PUBLISHED |
| Assigner | Linux |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2025-10-04 16:15:48 UTC |
| Updated | 2026-08-04 10:19:11 UTC |
| 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. |
Risk And Classification
Primary CVSS: v3.1 7.8 HIGH from [email protected]
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Problem Types: CWE-416
| Version | Source | Type | Score | Severity | Vector |
|---|---|---|---|---|---|
| 3.1 | [email protected] | Primary | 7.8 | HIGH | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| 3.1 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | Secondary | 7.8 | HIGH | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| 3.1 | CNA | DECLARED | 7.8 | HIGH | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
CVSS v3.1 Breakdown
Attack Vector
LocalAttack Complexity
LowPrivileges Required
LowUser Interaction
NoneScope
UnchangedConfidentiality
HighIntegrity
HighAvailability
HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVD Known Affected Configurations (CPE 2.3)
| Type | Vendor | Product | Version | Update | Edition | Language |
|---|---|---|---|---|---|---|
| Operating System | Linux | Linux Kernel | All | All | All | All |
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|---|---|---|---|
| CNA | Linux | Linux | affected 1b2628397058ebce7277480960b29c788138de90 701a8220762ff90615dc91d3543f789391b63298 git | Not specified |
| CNA | Linux | Linux | affected 1b2628397058ebce7277480960b29c788138de90 5bb4005fb667c6e2188fa87950f8d5faf2994410 git | Not specified |
| CNA | Linux | Linux | affected 1b2628397058ebce7277480960b29c788138de90 64ef787bb1588475163069c2e62fdd8f6c27b1f6 git | Not specified |
| CNA | Linux | Linux | affected 1b2628397058ebce7277480960b29c788138de90 809a5be62e92a444a3c3d7b9f438019d0b322f55 git | Not specified |
| CNA | Linux | Linux | affected 1b2628397058ebce7277480960b29c788138de90 5c62852942667c613de0458fc797c5b8c36112b5 git | Not specified |
| CNA | Linux | Linux | affected 1b2628397058ebce7277480960b29c788138de90 5c7cb94452901a93e90c2230632e2c12a681bc92 git | Not specified |
| CNA | Linux | Linux | affected 5.8 | Not specified |
| CNA | Linux | Linux | unaffected 5.8 semver | Not specified |
| CNA | Linux | Linux | unaffected 5.10.180 5.10.* semver | Not specified |
| CNA | Linux | Linux | unaffected 5.15.111 5.15.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.1.28 6.1.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.2.15 6.2.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.3.2 6.3.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.4 * original_commit_for_fix | Not specified |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| git.kernel.org/stable/c/809a5be62e92a444a3c3d7b9f438019d0b322f55 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | Patch |
| git.kernel.org/stable/c/701a8220762ff90615dc91d3543f789391b63298 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | Patch |
| git.kernel.org/stable/c/5bb4005fb667c6e2188fa87950f8d5faf2994410 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | Patch |
| git.kernel.org/stable/c/5c7cb94452901a93e90c2230632e2c12a681bc92 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | Patch |
| git.kernel.org/stable/c/64ef787bb1588475163069c2e62fdd8f6c27b1f6 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | Patch |
| git.kernel.org/stable/c/5c62852942667c613de0458fc797c5b8c36112b5 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | Patch |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.