CVE-2023-53810 (GCVE-0-2023-53810)
Vulnerability from cvelistv5 – Published: 2025-12-09 00:01 – Updated: 2025-12-09 00:01
VLAI?
Summary
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.
Severity ?
No CVSS data available.
Assigner
References
Impacted products
| Vendor | Product | Version | ||
|---|---|---|---|---|
| Linux | Linux |
Affected:
a892c8d52c02284076fbbacae6692aa5c5807d11 , < 874bdf43b4a7dc5463c31508f62b3e42eb237b08
(git)
Affected: a892c8d52c02284076fbbacae6692aa5c5807d11 , < d206f79d9cd658665b37ce8134c6ec849ac7af0c (git) Affected: a892c8d52c02284076fbbacae6692aa5c5807d11 , < 7d206ec7a04e8545828191b6ea8b49d3ea61391f (git) Affected: a892c8d52c02284076fbbacae6692aa5c5807d11 , < b278570e2c59d538216f8b656e97680188a8fba4 (git) Affected: a892c8d52c02284076fbbacae6692aa5c5807d11 , < 92d5d233b9ff531cf9cc36ab4251779e07adb633 (git) Affected: a892c8d52c02284076fbbacae6692aa5c5807d11 , < 9cd1e566676bbcb8a126acd921e4e194e6339603 (git) |
||
{
"containers": {
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"block/blk-crypto-internal.h",
"block/blk-crypto.c",
"block/blk-merge.c",
"block/blk-mq.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "874bdf43b4a7dc5463c31508f62b3e42eb237b08",
"status": "affected",
"version": "a892c8d52c02284076fbbacae6692aa5c5807d11",
"versionType": "git"
},
{
"lessThan": "d206f79d9cd658665b37ce8134c6ec849ac7af0c",
"status": "affected",
"version": "a892c8d52c02284076fbbacae6692aa5c5807d11",
"versionType": "git"
},
{
"lessThan": "7d206ec7a04e8545828191b6ea8b49d3ea61391f",
"status": "affected",
"version": "a892c8d52c02284076fbbacae6692aa5c5807d11",
"versionType": "git"
},
{
"lessThan": "b278570e2c59d538216f8b656e97680188a8fba4",
"status": "affected",
"version": "a892c8d52c02284076fbbacae6692aa5c5807d11",
"versionType": "git"
},
{
"lessThan": "92d5d233b9ff531cf9cc36ab4251779e07adb633",
"status": "affected",
"version": "a892c8d52c02284076fbbacae6692aa5c5807d11",
"versionType": "git"
},
{
"lessThan": "9cd1e566676bbcb8a126acd921e4e194e6339603",
"status": "affected",
"version": "a892c8d52c02284076fbbacae6692aa5c5807d11",
"versionType": "git"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"block/blk-crypto-internal.h",
"block/blk-crypto.c",
"block/blk-merge.c",
"block/blk-mq.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "5.8"
},
{
"lessThan": "5.8",
"status": "unaffected",
"version": "0",
"versionType": "semver"
},
{
"lessThanOrEqual": "5.10.*",
"status": "unaffected",
"version": "5.10.180",
"versionType": "semver"
},
{
"lessThanOrEqual": "5.15.*",
"status": "unaffected",
"version": "5.15.111",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.1.*",
"status": "unaffected",
"version": "6.1.28",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.2.*",
"status": "unaffected",
"version": "6.2.15",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.3.*",
"status": "unaffected",
"version": "6.3.2",
"versionType": "semver"
},
{
"lessThanOrEqual": "*",
"status": "unaffected",
"version": "6.4",
"versionType": "original_commit_for_fix"
}
]
}
],
"cpeApplicability": [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "5.10.180",
"versionStartIncluding": "5.8",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "5.15.111",
"versionStartIncluding": "5.8",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.1.28",
"versionStartIncluding": "5.8",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.2.15",
"versionStartIncluding": "5.8",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.3.2",
"versionStartIncluding": "5.8",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.4",
"versionStartIncluding": "5.8",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
]
}
],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nblk-mq: release crypto keyslot before reporting I/O complete\n\nOnce all I/O using a blk_crypto_key has completed, filesystems can call\nblk_crypto_evict_key(). However, the block layer currently doesn\u0027t call\nblk_crypto_put_keyslot() until the request is being freed, which happens\nafter upper layers have been told (via bio_endio()) the I/O has\ncompleted. This causes a race condition where blk_crypto_evict_key()\ncan see \u0027slot_refs != 0\u0027 without there being an actual bug.\n\nThis makes __blk_crypto_evict_key() hit the\n\u0027WARN_ON_ONCE(atomic_read(\u0026slot-\u003eslot_refs) != 0)\u0027 and return without\ndoing anything, eventually causing a use-after-free in\nblk_crypto_reprogram_all_keys(). (This is a very rare bug and has only\nbeen seen when per-file keys are being used with fscrypt.)\n\nThere are two options to fix this: either release the keyslot before\nbio_endio() is called on the request\u0027s last bio, or make\n__blk_crypto_evict_key() ignore slot_refs. Let\u0027s go with the first\nsolution, since it preserves the ability to report bugs (via\nWARN_ON_ONCE) where a key is evicted while still in-use."
}
],
"providerMetadata": {
"dateUpdated": "2025-12-09T00:01:08.062Z",
"orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"shortName": "Linux"
},
"references": [
{
"url": "https://git.kernel.org/stable/c/874bdf43b4a7dc5463c31508f62b3e42eb237b08"
},
{
"url": "https://git.kernel.org/stable/c/d206f79d9cd658665b37ce8134c6ec849ac7af0c"
},
{
"url": "https://git.kernel.org/stable/c/7d206ec7a04e8545828191b6ea8b49d3ea61391f"
},
{
"url": "https://git.kernel.org/stable/c/b278570e2c59d538216f8b656e97680188a8fba4"
},
{
"url": "https://git.kernel.org/stable/c/92d5d233b9ff531cf9cc36ab4251779e07adb633"
},
{
"url": "https://git.kernel.org/stable/c/9cd1e566676bbcb8a126acd921e4e194e6339603"
}
],
"title": "blk-mq: release crypto keyslot before reporting I/O complete",
"x_generator": {
"engine": "bippy-1.2.0"
}
}
},
"cveMetadata": {
"assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"assignerShortName": "Linux",
"cveId": "CVE-2023-53810",
"datePublished": "2025-12-09T00:01:08.062Z",
"dateReserved": "2025-12-08T23:58:35.276Z",
"dateUpdated": "2025-12-09T00:01:08.062Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2",
"vulnerability-lookup:meta": {
"nvd": "{\"cve\":{\"id\":\"CVE-2023-53810\",\"sourceIdentifier\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"published\":\"2025-12-09T01:16:53.073\",\"lastModified\":\"2025-12-09T18:37:13.640\",\"vulnStatus\":\"Awaiting Analysis\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"In the Linux kernel, the following vulnerability has been resolved:\\n\\nblk-mq: release crypto keyslot before reporting I/O complete\\n\\nOnce all I/O using a blk_crypto_key has completed, filesystems can call\\nblk_crypto_evict_key(). However, the block layer currently doesn\u0027t call\\nblk_crypto_put_keyslot() until the request is being freed, which happens\\nafter upper layers have been told (via bio_endio()) the I/O has\\ncompleted. This causes a race condition where blk_crypto_evict_key()\\ncan see \u0027slot_refs != 0\u0027 without there being an actual bug.\\n\\nThis makes __blk_crypto_evict_key() hit the\\n\u0027WARN_ON_ONCE(atomic_read(\u0026slot-\u003eslot_refs) != 0)\u0027 and return without\\ndoing anything, eventually causing a use-after-free in\\nblk_crypto_reprogram_all_keys(). (This is a very rare bug and has only\\nbeen seen when per-file keys are being used with fscrypt.)\\n\\nThere are two options to fix this: either release the keyslot before\\nbio_endio() is called on the request\u0027s last bio, or make\\n__blk_crypto_evict_key() ignore slot_refs. Let\u0027s go with the first\\nsolution, since it preserves the ability to report bugs (via\\nWARN_ON_ONCE) where a key is evicted while still in-use.\"}],\"metrics\":{},\"references\":[{\"url\":\"https://git.kernel.org/stable/c/7d206ec7a04e8545828191b6ea8b49d3ea61391f\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/874bdf43b4a7dc5463c31508f62b3e42eb237b08\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/92d5d233b9ff531cf9cc36ab4251779e07adb633\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/9cd1e566676bbcb8a126acd921e4e194e6339603\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/b278570e2c59d538216f8b656e97680188a8fba4\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/d206f79d9cd658665b37ce8134c6ec849ac7af0c\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"}]}}"
}
}
Loading…
Loading…
Sightings
| Author | Source | Type | Date |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Loading…
Loading…