{ "dataType": "CVE_RECORD", "dataVersion": "5.2", "cveMetadata": { "cveId": "CVE-2023-53536", "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "state": "PUBLISHED", "assignerShortName": "Linux", "dateReserved": "2025-10-04T15:14:15.919Z", "datePublished": "2025-10-04T15:16:47.304Z", "dateUpdated": "2026-08-05T09:14:40.430Z" }, "containers": { "cna": { "providerMetadata": { "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "shortName": "Linux", "dateUpdated": "2026-08-05T09:14:40.430Z" }, "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nblk-crypto: make blk_crypto_evict_key() more robust\n\nIf blk_crypto_evict_key() sees that the key is still in-use (due to a\nbug) or that ->keyslot_evict failed, it currently just returns while\nleaving the key linked into the keyslot management structures.\n\nHowever, blk_crypto_evict_key() is only called in contexts such as inode\neviction where failure is not an option. So actually the caller\nproceeds with freeing the blk_crypto_key regardless of the return value\nof blk_crypto_evict_key().\n\nThese two assumptions don't match, and the result is that there can be a\nuse-after-free in blk_crypto_reprogram_all_keys() after one of these\nerrors occurs. (Note, these errors *shouldn't* happen; we're just\ntalking about what happens if they do anyway.)\n\nFix this by making blk_crypto_evict_key() unlink the key from the\nkeyslot management structures even on failure.\n\nAlso improve some comments." } ], "metrics": [ { "cvssV3_1": { "version": "3.1", "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H", "baseScore": 7.8, "baseSeverity": "HIGH" }, "scenarios": [ { "lang": "en", "value": "AV:L - The vulnerable path is reached through ordinary filesystem syscalls (create/write/unlink causing inode eviction) on a locally-mounted fscrypt-encrypted volume backed by UFS/eMMC inline-crypto hardware; there is no remote protocol handler involved.\nAC:L - The attacker drives the eviction side of the race directly and can retry unboundedly — a tight create/write/unlink loop over per-file-key files generates thousands of `blk_crypto_evict_key()` calls per second against in-flight blk-mq requests, and UFS runtime-PM resume (which calls `blk_crypto_reprogram_all_keys()`) can be induced by alternating I/O bursts with idle periods.\nPR:L - Only an unprivileged local account with write access to an fscrypt-encrypted directory is needed — any sandboxed Android app in its own `/data/data` directory, or any user with an encrypted home — and no capability or namespace check exists anywhere on the path from `evict_inode()` to `__blk_crypto_evict_key()`.\nUI:N - The attacker performs every step itself — writing files, forcing inode eviction, and idling the device to provoke a controller reset — with no action required from any other user or administrator.\nS:U - The use-after-free occurs on a kernel heap object and is exploited within the kernel's own security authority; no VM, IOMMU, or hypervisor boundary is crossed.\nC:H - The freed object is a `struct blk_crypto_key` holding raw key material, and `blk_crypto_reprogram_all_keys()` reads it after free and programs the (groomable) contents into a hardware keyslot; additionally the stale pointer-keyed hash entry causes a reallocated key to reuse a slot holding a different key, exposing file plaintext across encryption boundaries, and the UAF read primitive is generally leverageable for kernel memory disclosure.\nI:H - A use-after-free on a slab object whose lifetime the attacker controls permits heap spraying to place attacker-chosen data where the kernel expects a key, yielding a write/control primitive; independently, the wrong-key confusion silently encrypts user data at rest under the wrong key, corrupting it irrecoverably.\nA:H - Dereferencing the freed `blk_crypto_key` in `blk_crypto_reprogram_all_keys()` causes an oops or panic (plus the `WARN_ON_ONCE`/`WARN_ON` splats), and the attacker can repeat the trigger loop indefinitely to crash the system." } ] } ], "affected": [ { "product": "Linux", "vendor": "Linux", "defaultStatus": "unaffected", "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git", "programFiles": [ "block/blk-crypto-profile.c", "block/blk-crypto.c" ], "versions": [ { "version": "1b2628397058ebce7277480960b29c788138de90", "lessThan": "701a8220762ff90615dc91d3543f789391b63298", "status": "affected", "versionType": "git" }, { "version": "1b2628397058ebce7277480960b29c788138de90", "lessThan": "5bb4005fb667c6e2188fa87950f8d5faf2994410", "status": "affected", "versionType": "git" }, { "version": "1b2628397058ebce7277480960b29c788138de90", "lessThan": "64ef787bb1588475163069c2e62fdd8f6c27b1f6", "status": "affected", "versionType": "git" }, { "version": "1b2628397058ebce7277480960b29c788138de90", "lessThan": "809a5be62e92a444a3c3d7b9f438019d0b322f55", "status": "affected", "versionType": "git" }, { "version": "1b2628397058ebce7277480960b29c788138de90", "lessThan": "5c62852942667c613de0458fc797c5b8c36112b5", "status": "affected", "versionType": "git" }, { "version": "1b2628397058ebce7277480960b29c788138de90", "lessThan": "5c7cb94452901a93e90c2230632e2c12a681bc92", "status": "affected", "versionType": "git" } ] }, { "product": "Linux", "vendor": "Linux", "defaultStatus": "affected", "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git", "programFiles": [ "block/blk-crypto-profile.c", "block/blk-crypto.c" ], "versions": [ { "version": "5.8", "status": "affected" }, { "version": "0", "lessThan": "5.8", "status": "unaffected", "versionType": "semver" }, { "version": "5.10.180", "lessThanOrEqual": "5.10.*", "status": "unaffected", "versionType": "semver" }, { "version": "5.15.111", "lessThanOrEqual": "5.15.*", "status": "unaffected", "versionType": "semver" }, { "version": "6.1.28", "lessThanOrEqual": "6.1.*", "status": "unaffected", "versionType": "semver" }, { "version": "6.2.15", "lessThanOrEqual": "6.2.*", "status": "unaffected", "versionType": "semver" }, { "version": "6.3.2", "lessThanOrEqual": "6.3.*", "status": "unaffected", "versionType": "semver" }, { "version": "6.4", "lessThanOrEqual": "*", "status": "unaffected", "versionType": "original_commit_for_fix" } ] } ], "cpeApplicability": [ { "nodes": [ { "operator": "OR", "negate": false, "cpeMatch": [ { "vulnerable": true, "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "versionStartIncluding": "5.8", "versionEndExcluding": "5.10.180" }, { "vulnerable": true, "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "versionStartIncluding": "5.8", "versionEndExcluding": "5.15.111" }, { "vulnerable": true, "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "versionStartIncluding": "5.8", "versionEndExcluding": "6.1.28" }, { "vulnerable": true, "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "versionStartIncluding": "5.8", "versionEndExcluding": "6.2.15" }, { "vulnerable": true, "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "versionStartIncluding": "5.8", "versionEndExcluding": "6.3.2" }, { "vulnerable": true, "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "versionStartIncluding": "5.8", "versionEndExcluding": "6.4" } ] } ] } ], "references": [ { "url": "https://git.kernel.org/stable/c/701a8220762ff90615dc91d3543f789391b63298" }, { "url": "https://git.kernel.org/stable/c/5bb4005fb667c6e2188fa87950f8d5faf2994410" }, { "url": "https://git.kernel.org/stable/c/64ef787bb1588475163069c2e62fdd8f6c27b1f6" }, { "url": "https://git.kernel.org/stable/c/809a5be62e92a444a3c3d7b9f438019d0b322f55" }, { "url": "https://git.kernel.org/stable/c/5c62852942667c613de0458fc797c5b8c36112b5" }, { "url": "https://git.kernel.org/stable/c/5c7cb94452901a93e90c2230632e2c12a681bc92" } ], "title": "blk-crypto: make blk_crypto_evict_key() more robust", "x_generator": { "engine": "bippy-1.2.0" } } } }