CVE-2023-53810blk-mq: release crypto keyslot before reporting I/O complete
- 7.8HighCVSS base score
- 0.15%Exploitation in 30 daysEPSS · top 96% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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.
Timeline
ID reserved
By Linux
- 1 day later
· 1 day later
Published
- 8 months later
· 8 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| LinuxCNA (assigner) | 3.1 | High7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVDNVD · Deferred | 3.1 | High7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
- EPSS (exploitation in 30 days)
- 0.15% · top 96% of all CVEs (17 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.
Affected products
- affected a892c8d52c02284076fbbacae6692aa5c5807d11 – < 874bdf43b4a7dc5463c31508f62b3e42eb237b08
- affected a892c8d52c02284076fbbacae6692aa5c5807d11 – < d206f79d9cd658665b37ce8134c6ec849ac7af0c
- affected a892c8d52c02284076fbbacae6692aa5c5807d11 – < 7d206ec7a04e8545828191b6ea8b49d3ea61391f
- affected a892c8d52c02284076fbbacae6692aa5c5807d11 – < b278570e2c59d538216f8b656e97680188a8fba4
- affected a892c8d52c02284076fbbacae6692aa5c5807d11 – < 92d5d233b9ff531cf9cc36ab4251779e07adb633
- affected a892c8d52c02284076fbbacae6692aa5c5807d11 – < 9cd1e566676bbcb8a126acd921e4e194e6339603
- affected 5.8
- unaffected < 5.8
- unaffected 5.10.180 – ≤ 5.10.*
- unaffected 5.15.111 – ≤ 5.15.*
- unaffected 6.1.28 – ≤ 6.1.*
- unaffected 6.2.15 – ≤ 6.2.*
- unaffected 6.3.2 – ≤ 6.3.*
- unaffected 6.4 – ≤ *
References
References6
- https://git.kernel.org/stable/c/874bdf43b4a7dc5463c31508f62b3e42eb237b08 (opens in a new tab)
- https://git.kernel.org/stable/c/d206f79d9cd658665b37ce8134c6ec849ac7af0c (opens in a new tab)
- https://git.kernel.org/stable/c/7d206ec7a04e8545828191b6ea8b49d3ea61391f (opens in a new tab)
- https://git.kernel.org/stable/c/b278570e2c59d538216f8b656e97680188a8fba4 (opens in a new tab)
- https://git.kernel.org/stable/c/92d5d233b9ff531cf9cc36ab4251779e07adb633 (opens in a new tab)
- https://git.kernel.org/stable/c/9cd1e566676bbcb8a126acd921e4e194e6339603 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2023-60096 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2023-53810)Record last updated .