NVD / CVE Program· CNA Linux

CVE-2023-53536: blk-crypto: make blk_crypto_evict_key() more robust

Noroxi assessment

Priority: Monitor (action score 31/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.16% (FIRST EPSS).
Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
Fixed version: Linux Linux 5bb4005fb667c6e2188fa87950f8d5faf2994410, 5c62852942667c613de0458fc797c5b8c36112b5, 5c7cb94452901a93e90c2230632e2c12a681bc92.

Low priority for now. Upgrade to Linux Linux 5bb4005fb667c6e2188fa87950f8d5faf2994410, 5c62852942667c613de0458fc797c5b8c36112b5, 5c7cb94452901a93e90c2230632e2c12a681bc92 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

HighCVSS 7.8 · v3.1—No exploit Fix available

Memory safety

BDU:2026-12394

Published: Oct 4, 2025
Updated: Aug 5, 2026
EPSS: 0.1% · 5th percentile
CWE: CWE-416

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 31 / 40 · 7.8 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.1%

CNA vs NVD score

NVD: 7.8
CNA · Linux: 7.8; agree

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
linux	linux kernel	cpe:2.3:o:linux:linux_kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

linux linux kernel5.8 and later · before 5.10.180
linux linux kernel5.11 and later · before 5.15.111
linux linux kernel5.16 and later · before 6.1.28
linux linux kernel6.2 and later · before 6.2.15
linux linux kernel6.3 and later · before 6.3.2

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

Linux Linux
- 5.8affected
- 1b2628397058ebce7277480960b29c788138de90 and later · before 701a8220762ff90615dc91d3543f789391b63298affected · git
- 1b2628397058ebce7277480960b29c788138de90 and later · before 5bb4005fb667c6e2188fa87950f8d5faf2994410affected · git
- 1b2628397058ebce7277480960b29c788138de90 and later · before 64ef787bb1588475163069c2e62fdd8f6c27b1f6affected · git
- 1b2628397058ebce7277480960b29c788138de90 and later · before 809a5be62e92a444a3c3d7b9f438019d0b322f55affected · git
- 1b2628397058ebce7277480960b29c788138de90 and later · before 5c62852942667c613de0458fc797c5b8c36112b5affected · git
- 1b2628397058ebce7277480960b29c788138de90 and later · before 5c7cb94452901a93e90c2230632e2c12a681bc92affected · git
- before 5.8not affected · semver
- 5.10.180 and later · up to and including 5.10.*not affected · semver
- 5.15.111 and later · up to and including 5.15.*not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
Debian:12	linux	before 6.1.37-1	6.1.37-1
Debian:13	linux	before 6.3.7-1	6.3.7-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
90Now
CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
89Now
CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
85Now

Published before and after this one in the same product

← EarlierCVE-2023-53533Oct 4, 2025 · Input: raspberrypi-ts - fix refcount leak in rpi_ts_probe
22Monitor
← EarlierCVE-2023-53534Oct 4, 2025 · drm/mediatek: mtk_drm_crtc: Add checks for devm_kcalloc
22Monitor
Later →CVE-2023-53537Oct 4, 2025 · f2fs: fix to avoid use-after-free for cached IPU bio
31Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
Linux Linux	5bb4005fb667c6e2188fa87950f8d5faf2994410	Vendor (CNA)
Linux Linux	5c62852942667c613de0458fc797c5b8c36112b5	Vendor (CNA)
Linux Linux	5c7cb94452901a93e90c2230632e2c12a681bc92	Vendor (CNA)
Linux Linux	64ef787bb1588475163069c2e62fdd8f6c27b1f6	Vendor (CNA)
Linux Linux	701a8220762ff90615dc91d3543f789391b63298	Vendor (CNA)
Linux Linux	809a5be62e92a444a3c3d7b9f438019d0b322f55	Vendor (CNA)
debian:linux	6.1.37-1 · Debian:12	Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

Someone with local access to the system can trigger it.
A low-privileged account is enough.
No user action is required.
No special conditions are required; it is repeatable.

If successful

Confidentiality: high · data can be read
Integrity: high · data or configuration can be modified
Availability: high · the service can be disrupted

Attack vector: Local
Attack complexity: Low
Privileges required: Low
User interaction: None
Scope: Unchanged
Confidentiality impact: High
Integrity impact: High
Availability impact: High

Weakness class (CWE)

CWE-416 · Use After Free

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

nvd-primary

Root cause

After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.

The bug in code

The whole CWE-416 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1free(dev->buf);
2/* ... another thread is still running ... */
3process(dev->buf);

Fixed

1lock(&dev->lock);
2free(dev->buf);
3dev->buf = NULL;
4unlock(&dev->lock);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

Fix✗ → ✓Sep 28, 2026, 10:08 PM UTC

For records you follow, these changes also arrive as notifications. →

References

git.kernel.org/stable/c/5bb4005fb667c6e2188fa87950f8d5faf2994410

Show all references (5 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records