CVE-2023-53536 json
blk-crypto: make blk_crypto_evict_key() more robust
published 2025-10-04 13 mo ago modified 2026-08-05 3 mo ago also EUVD-2025-32342
- cvss
- 7.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 5%
- public exploits
- 0
- none known
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.
Patch / fix
- Linux Linux 5.10.180, 5.15.111, 6.1.28, 6.2.15, 6.3.2, 6.4
- linux Debian 12 6.1.37-1
- linux Debian 14, Debian 13 6.3.7-1
debian advisories DEBIAN-CVE-2023-53536
- linux Ubuntu 22.04 LTS 5.15.0-79.86
- linux-aws Ubuntu 22.04 LTS 5.15.0-1042.47
- linux-gcp Ubuntu 22.04 LTS 5.15.0-1039.47
- linux-gke Ubuntu 22.04 LTS 5.15.0-1039.44
- linux-ibm Ubuntu 22.04 LTS 5.15.0-1035.38
- linux-kvm Ubuntu 22.04 LTS 5.15.0-1039.44
- linux-azure Ubuntu 22.04 LTS 5.15.0-1045.52
- linux-gkeop Ubuntu 22.04 LTS 5.15.0-1025.30
ubuntu advisories UBUNTU-CVE-2023-53536
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- kernel RHEL 9 5.14.0-427.13.1.el9_4
- rv RHEL 9 5.14.0-427.13.1.el9_4
- perf RHEL 9 5.14.0-427.13.1.el9_4
- rtla RHEL 9 5.14.0-427.13.1.el9_4
- bpftool RHEL 9 7.3.0-427.13.1.el9_4
- libperf RHEL 9 5.14.0-427.13.1.el9_4
- kernel-rt RHEL 9 5.14.0-427.13.1.el9_4
- kernel-64k RHEL 9 5.14.0-427.13.1.el9_4
red hat advisories RHSA-2024:2394
- git.kernel.org/stable/c/701a8220762ff90615dc91d3543f789391b63298 commit
- git.kernel.org/stable/c/5bb4005fb667c6e2188fa87950f8d5faf2994410 commit
- git.kernel.org/stable/c/64ef787bb1588475163069c2e62fdd8f6c27b1f6 commit
- git.kernel.org/stable/c/809a5be62e92a444a3c3d7b9f438019d0b322f55 commit
- git.kernel.org/stable/c/5c62852942667c613de0458fc797c5b8c36112b5 commit
- git.kernel.org/stable/c/5c7cb94452901a93e90c2230632e2c12a681bc92 commit
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2023-53536 updated cvss 5.5
kernel: blk-crypto: make blk_crypto_evict_key() more robust
-
Red Hat Enterprise Linux 9 kernel-rt, kernel-rt-kvm, kernel-rt-core, kernel-rt-modules, kernel-rt-debug-kvm, kernel-rt-debug-core, +12 moreaffected: no fix available “Fix deferred”
-
Red Hat Enterprise Linux AppStream (v. 9) rv 5.14.0-427.13.1.el9_4, perf 5.14.0-427.13.1.el9_4, rtla 5.14.0-427.13.1.el9_4, kernel-devel-matched 5.14.0-427.13.1.el9_4, kernel-64k-devel-matched 5.14.0-427.13.1.el9_4, kernel-debug-devel-matched 5.14.0-427.13.1.el9_4, +6 more Red Hat Enterprise Linux BaseOS (v. 9) bpftool 7.3.0-427.13.1.el9_4, kernel 5.14.0-427.13.1.el9_4, kernel-64k 5.14.0-427.13.1.el9_4, kernel-core 5.14.0-427.13.1.el9_4, kernel-tools 5.14.0-427.13.1.el9_4, python3-perf 5.14.0-427.13.1.el9_4, +28 more Red Hat Enterprise Linux CRB (v. 9) libperf 5.14.0-427.13.1.el9_4, kernel-debuginfo-common-s390x 5.14.0-427.13.1.el9_4, kernel-debuginfo-common-x86_64 5.14.0-427.13.1.el9_4, kernel-debuginfo-common-aarch64 5.14.0-427.13.1.el9_4, kernel-debuginfo-common-ppc64le 5.14.0-427.13.1.el9_4 Red Hat Enterprise Linux NFV (v. 9) kernel-rt 5.14.0-427.13.1.el9_4, kernel-rt-kvm 5.14.0-427.13.1.el9_4, kernel-rt-core 5.14.0-427.13.1.el9_4, kernel-rt-modules 5.14.0-427.13.1.el9_4, kernel-rt-debug-kvm 5.14.0-427.13.1.el9_4, kernel-rt-debug-core 5.14.0-427.13.1.el9_4, +6 more Red Hat Enterprise Linux RT (v. 9) kernel-rt 5.14.0-427.13.1.el9_4, kernel-rt-core 5.14.0-427.13.1.el9_4, kernel-rt-modules 5.14.0-427.13.1.el9_4, kernel-rt-debug-core 5.14.0-427.13.1.el9_4, kernel-rt-modules-core 5.14.0-427.13.1.el9_4, kernel-rt-debug-modules 5.14.0-427.13.1.el9_4, +4 morefixed: vendor fix RHSA-2024:2394
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 10 kernelnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.16% chance of exploitation in the next 30 days, higher than 5% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVD | 3.1 | 7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
Affected products
- Linux Linux
Classification
- Weakness
-
- CWE-416 Use After Free
- Technology feeds
References
-
git.kernel.org
/stable/c/701a8220762ff90615dc91d3543f789391b63298
patch
-
git.kernel.org
/stable/c/5bb4005fb667c6e2188fa87950f8d5faf2994410
patch
-
git.kernel.org
/stable/c/64ef787bb1588475163069c2e62fdd8f6c27b1f6
patch
-
git.kernel.org
/stable/c/809a5be62e92a444a3c3d7b9f438019d0b322f55
patch
-
git.kernel.org
/stable/c/5c62852942667c613de0458fc797c5b8c36112b5
patch
-
git.kernel.org
/stable/c/5c7cb94452901a93e90c2230632e2c12a681bc92
patch
Sources
- CVE List CVE-2023-53536
- NVD CVE-2023-53536
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.