Answer in brief
CVE-2023-53536 records a High severity (CVSS 7.8) vulnerability in blk-crypto: make blk_crypto_evict_key() more robust. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=1b2628397058ebce7277480960b29c788138de90 <701a8220762ff90615dc91d3543f789391b63298 || >=1b2628397058ebce7277480960b29c788138de90 <5bb4005fb667c6e2188fa87950f8d5faf2994410 || >=1b2628397058ebce7277480960b29c788138de90 <64ef787bb1588475163069c2e62fdd8f6c27b1f6 || >=1b2628397058ebce7277480960b29c788138de90 <809a5be62e92a444a3c3d7b9f438019d0b322f55 || >=1b2628397058ebce7277480960b29c788138de90 <5c62852942667c613de0458fc797c5b8c36112b5 || >=1b2628397058ebce7277480960b29c788138de90 <5c7cb94452901a93e90c2230632e2c12a681bc92 | 701a8220762ff90615dc91d3543f789391b63298, 5bb4005fb667c6e2188fa87950f8d5faf2994410, 64ef787bb1588475163069c2e62fdd8f6c27b1f6, 809a5be62e92a444a3c3d7b9f438019d0b322f55, 5c62852942667c613de0458fc797c5b8c36112b5, 5c7cb94452901a93e90c2230632e2c12a681bc92 |
| Linux/Linuxgeneric | 5.8 | Not reported |
Published upstream
Oct 4, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 4, 2026
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.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2023-53536 records a High severity (CVSS 7.8) vulnerability in blk-crypto: make blk_crypto_evict_key() more robust. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=1b2628397058ebce7277480960b29c788138de90 <701a8220762ff90615dc91d3543f789391b63298 || >=1b2628397058ebce7277480960b29c788138de90 <5bb4005fb667c6e2188fa87950f8d5faf2994410 || >=1b2628397058ebce7277480960b29c788138de90 <64ef787bb1588475163069c2e62fdd8f6c27b1f6 || >=1b2628397058ebce7277480960b29c788138de90 <809a5be62e92a444a3c3d7b9f438019d0b322f55 || >=1b2628397058ebce7277480960b29c788138de90 <5c62852942667c613de0458fc797c5b8c36112b5 || >=1b2628397058ebce7277480960b29c788138de90 <5c7cb94452901a93e90c2230632e2c12a681bc92 | 701a8220762ff90615dc91d3543f789391b63298, 5bb4005fb667c6e2188fa87950f8d5faf2994410, 64ef787bb1588475163069c2e62fdd8f6c27b1f6, 809a5be62e92a444a3c3d7b9f438019d0b322f55, 5c62852942667c613de0458fc797c5b8c36112b5, 5c7cb94452901a93e90c2230632e2c12a681bc92 |
| Linux/Linuxgeneric | 5.8 | Not reported |
Published upstream
Oct 4, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 4, 2026
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.
Quoted source text, attributed separately from HOL analysis.