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 *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.
- Products
- Kernel
- Affected versions
- Not specified
- Fixed versions
- 5.10.180, 5.15.111, 6.1.28, 6.2.15, 6.3.2
- CVEs
- CVE-2023-53536
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 2 Nov 2026, 21:48 UTC · Revision 1
Source evidence
blk-crypto: make blk_crypto_evict_key() more robust
core-osv · Original sourcePublished 4 Oct 2025, 15:16 UTC
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.
osv:CVE-2023-53536
Kernel
Fixed versions: 5.10.180, 5.15.111, 6.1.28, 6.2.15, 6.3.2
Complete source record
{
"id": "383ad7c6b4a428ba3e160ef77c926b5afc6d83d8670c26153fa8973d9ea821d8",
"url": "https://osv.dev/vulnerability/CVE-2023-53536",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "blk-crypto: make blk_crypto_evict_key() more robust",
"summary": "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.",
"evidence": "osv:CVE-2023-53536",
"products": [
{
"name": {
"value": "Kernel",
"evidence": "/affected/1/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "5.10.180",
"evidence": "/affected/1/ranges"
},
{
"value": "5.15.111",
"evidence": "/affected/1/ranges"
},
{
"value": "6.1.28",
"evidence": "/affected/1/ranges"
},
{
"value": "6.2.15",
"evidence": "/affected/1/ranges"
},
{
"value": "6.3.2",
"evidence": "/affected/1/ranges"
}
],
"affected_versions": []
}
],
"severity": "high",
"structured": {
"id": "CVE-2023-53536",
"aliases": [
"CVE-2023-53536"
],
"metrics": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H"
}
],
"affected": [
{
"ranges": [
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "1b2628397058ebce7277480960b29c788138de90"
},
{
"fixed": "701a8220762ff90615dc91d3543f789391b63298"
},
{
"fixed": "5bb4005fb667c6e2188fa87950f8d5faf2994410"
},
{
"fixed": "64ef787bb1588475163069c2e62fdd8f6c27b1f6"
},
{
"fixed": "809a5be62e92a444a3c3d7b9f438019d0b322f55"
},
{
"fixed": "5c62852942667c613de0458fc797c5b8c36112b5"
},
{
"fixed": "5c7cb94452901a93e90c2230632e2c12a681bc92"
}
]
}
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2023-53536.json"
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.8.0"
},
{
"fixed": "5.10.180"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.11.0"
},
{
"fixed": "5.15.111"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.16.0"
},
{
"fixed": "6.1.28"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.2.0"
},
{
"fixed": "6.2.15"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.3.0"
},
{
"fixed": "6.3.2"
}
]
}
],
"package": {
"name": "Kernel",
"ecosystem": "Linux"
},
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2023-53536.json"
}
}
],
"modified": "2026-10-28T02:30:24.178764258Z",
"provider": "osv",
"references": [
"https://git.kernel.org/stable/c/5bb4005fb667c6e2188fa87950f8d5faf2994410",
"https://git.kernel.org/stable/c/5c62852942667c613de0458fc797c5b8c36112b5",
"https://git.kernel.org/stable/c/5c7cb94452901a93e90c2230632e2c12a681bc92",
"https://git.kernel.org/stable/c/64ef787bb1588475163069c2e62fdd8f6c27b1f6",
"https://git.kernel.org/stable/c/701a8220762ff90615dc91d3543f789391b63298",
"https://git.kernel.org/stable/c/809a5be62e92a444a3c3d7b9f438019d0b322f55",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2023/53xxx/CVE-2023-53536.json",
"https://nvd.nist.gov/vuln/detail/CVE-2023-53536",
"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
],
"provider_metadata": {
"cna_assigner": "Linux",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2023/53xxx/CVE-2023-53536.json"
}
},
"related_cves": [
{
"value": "CVE-2023-53536",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 490357,
"published_at": "2025-10-04T15:16:47.304+00:00"
}