CVE-2023-53536
published 2025-10-04CVE-2023-53536: 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…
PriorityP338high7.8CVSS 3.1
AVLACLPRLUINSUCHIHAH
EPSS
0.15%
4.6th percentile
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.
Affected
17 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | linux | < linux 6.1.37-1 (bookworm) | linux 6.1.37-1 (bookworm) |
| linux | linux | — | — |
| linux | linux | >= 1b2628397058ebce7277480960b29c788138de90 < 701a8220762ff90615dc91d3543f789391b63298 | 701a8220762ff90615dc91d3543f789391b63298 |
| linux | linux | >= 1b2628397058ebce7277480960b29c788138de90 < 5bb4005fb667c6e2188fa87950f8d5faf2994410 | 5bb4005fb667c6e2188fa87950f8d5faf2994410 |
| linux | linux | >= 1b2628397058ebce7277480960b29c788138de90 < 64ef787bb1588475163069c2e62fdd8f6c27b1f6 | 64ef787bb1588475163069c2e62fdd8f6c27b1f6 |
| linux | linux | >= 1b2628397058ebce7277480960b29c788138de90 < 809a5be62e92a444a3c3d7b9f438019d0b322f55 | 809a5be62e92a444a3c3d7b9f438019d0b322f55 |
| linux | linux | >= 1b2628397058ebce7277480960b29c788138de90 < 5c62852942667c613de0458fc797c5b8c36112b5 | 5c62852942667c613de0458fc797c5b8c36112b5 |
| linux | linux | >= 1b2628397058ebce7277480960b29c788138de90 < 5c7cb94452901a93e90c2230632e2c12a681bc92 | 5c7cb94452901a93e90c2230632e2c12a681bc92 |
| linux | linux_kernel | >= 0 < 5.10.191-1 | 5.10.191-1 |
| linux | linux_kernel | >= 0 < 6.1.37-1 | 6.1.37-1 |
| linux | linux_kernel | >= 0 < 6.3.7-1 | 6.3.7-1 |
| linux | linux_kernel | >= 0 < 6.3.7-1 | 6.3.7-1 |
| linux | linux_kernel | >= 5.11 < 5.15.111 | 5.15.111 |
| linux | linux_kernel | >= 5.16 < 6.1.28 | 6.1.28 |
| linux | linux_kernel | >= 5.8 < 5.10.180 | 5.10.180 |
| linux | linux_kernel | >= 6.2 < 6.2.15 | 6.2.15 |
| linux | linux_kernel | >= 6.3 < 6.3.2 | 6.3.2 |
CVSS provenance
nvdv3.17.8HIGHCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
osv7.8HIGH
vendor_debian7.8HIGH
vendor_redhat7.8HIGH
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
OSV
CVE-2023-53536: 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
osv·2025-10-04·CVSS 7.8
CVE-2023-53536 [HIGH] CVE-2023-53536: 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
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
GHSA
GHSA-f2cg-q42r-r6f6: In the Linux kernel, the following vulnerability has been resolved:
blk-crypto: make blk_crypto_evict_key() more robust
If blk_crypto_evict_key() se
ghsa_unreviewed·2025-10-04
CVE-2023-53536 [HIGH] CWE-416 GHSA-f2cg-q42r-r6f6: In the Linux kernel, the following vulnerability has been resolved:
blk-crypto: make blk_crypto_evict_key() more robust
If blk_crypto_evict_key() se
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
Red Hat
kernel: blk-crypto: make blk_crypto_evict_key() more robust
vendor_redhat·2025-10-04·CVSS 7.8
CVE-2023-53536 [HIGH] CWE-825 kernel: blk-crypto: make blk_crypto_evict_key() more robust
kernel: blk-crypto: make blk_crypto_evict_key() more robust
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 *sho
Debian
CVE-2023-53536: linux - In the Linux kernel, the following vulnerability has been resolved: blk-crypto:...
vendor_debian·2023·CVSS 7.8
CVE-2023-53536 [HIGH] CVE-2023-53536: linux - In the Linux kernel, the following vulnerability has been resolved: blk-crypto:...
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
No detection rules found.
No public exploits indexed.
https://git.kernel.org/stable/c/5bb4005fb667c6e2188fa87950f8d5faf2994410https://git.kernel.org/stable/c/5c62852942667c613de0458fc797c5b8c36112b5https://git.kernel.org/stable/c/5c7cb94452901a93e90c2230632e2c12a681bc92https://git.kernel.org/stable/c/64ef787bb1588475163069c2e62fdd8f6c27b1f6https://git.kernel.org/stable/c/701a8220762ff90615dc91d3543f789391b63298https://git.kernel.org/stable/c/809a5be62e92a444a3c3d7b9f438019d0b322f55
2025-10-04
Published