CVE-2023-53810 Details
Description
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.
A race condition vulnerability has been identified in the Linux kernel's block layer, specifically within the block-mq I/O scheduler. This issue arises because the block layer does not release the keyslot associated with a crypto key until the I/O request is being freed. Consequently, upper layers are notified that the I/O has completed before the keyslot is released, leading to a situation where the key eviction function can incorrectly perceive that a keyslot is still in use. This mismanagement causes a use-after-free error, particularly when per-file encryption keys are used with the fscrypt feature. The vulnerability has been addressed by modifying the block layer to release the keyslot before signaling the completion of the I/O request.
Users can upgrade to the patched version of the Linux kernel where this vulnerability has been addressed. Instructions for downloading the latest stable kernel can be found on the official Linux kernel website.
Metrics
CVSS 4.0 Severity and Vector Strings:
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
Volerion
Assessed Dec 9, 2025References 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/7d206ec7a04e8545828191b6ea8b49d3ea61391f | kernel.org | Source CodeVendor |
| https://git.kernel.org/stable/c/874bdf43b4a7dc5463c31508f62b3e42eb237b08 | kernel.org | Source CodeVendor |
| https://git.kernel.org/stable/c/92d5d233b9ff531cf9cc36ab4251779e07adb633 | kernel.org | Source CodeVendor |
| https://git.kernel.org/stable/c/9cd1e566676bbcb8a126acd921e4e194e6339603 | kernel.org | Source CodeVendor |
| https://git.kernel.org/stable/c/b278570e2c59d538216f8b656e97680188a8fba4 | kernel.org | Source CodeVendor |
| https://git.kernel.org/stable/c/d206f79d9cd658665b37ce8134c6ec849ac7af0c | kernel.org | Source CodeVendor |
Weakness Enumeration
No weakness enumeration is available for this CVE.
Affected Products
| Product | Versions |
|---|---|
| Linux kernel | All versions |
CPE
Remediation
| |
Change History
3 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Aug 4, 2026 | CVE Modified | kernel.org |
| Jun 17, 2026 | CVE Modified | kernel.org |
| Dec 9, 2025 | New CVE Received | kernel.org |
Volerion