NVD / CVE Program· CNA Linux

CVE-2025-21739: scsi: ufs: core: Fix use-after free in init error and remove paths

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.22% (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 0a6895c03b1f439236e2d22b1a69ebfc1eb9d5ea, 0c77c0d754fe83cb154715fcfec6c3faef94f207, 0dc539b888fb5f56b6eeddd95433eab557d4b0c1; azl3 kernel 6.6.134.1-2 on Azure Linux 3.0 6.6.137.1-2.

Low priority for now. Upgrade to Linux Linux 0a6895c03b1f439236e2d22b1a69ebfc1eb9d5ea, 0c77c0d754fe83cb154715fcfec6c3faef94f207, 0dc539b888fb5f56b6eeddd95433eab557d4b0c1; azl3 kernel 6.6.134.1-2 on Azure Linux 3.0 6.6.137.1-2 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: scsi: ufs: core: Fix use-after free in init error and remove paths devm_blk_crypto_profile_init() registers a cleanup handler to run when the associated (platform-) device is being released. For UFS, the crypto private data and pointers are stored as part of the ufs_hba's data structure 'struct ufs_hba::crypto_profile'. This structure is allocated as part of the underlying ufshcd and therefore Scsi_host allocation. During driver release or during error handling in ufshcd_pltfrm_init(), this structure is released as part of ufshcd_dealloc_host() before the (platform-) device associated with the crypto call above is released. Once this device is released, the crypto cleanup code will run, using the just-released 'struct ufs_hba::crypto_profile'. This causes a use-after-free situation: Call trace: kfree+0x60/0x2d8 (P) kvfree+0x44/0x60 blk_crypto_profile_destroy_callback+0x28/0x70 devm_action_release+0x1c/0x30 release_nodes+0x6c/0x108 devres_release_all+0x98/0x100 device_unbind_cleanup+0x20/0x70 really_probe+0x218/0x2d0 In other words, the initialisation code flow is: platform-device probe ufshcd_pltfrm_init() ufshcd_alloc_host() scsi_host_alloc() allocation of struct ufs_hba creation of scsi-host devices devm_blk_crypto_profile_init() devm registration of cleanup handler using platform-device and during error handling of ufshcd_pltfrm_init() or during driver removal: ufshcd_dealloc_host() scsi_host_put() put_device(scsi-host) release of struct ufs_hba put_device(platform-device) crypto cleanup handler To fix this use-after free, change ufshcd_alloc_host() to register a devres action to automatically cleanup the underlying SCSI device on ufshcd destruction, without requiring explicit calls to ufshcd_dealloc_host(). This way: * the crypto profile and all other ufs_hba-owned resources are destroyed before SCSI (as they've been registered after) * a memleak is plugged in tc-dwc-g210-pci.c remove() as a side-effect * EXPORT_SYMBOL_GPL(ufshcd_dealloc_host) can be removed fully as it's not needed anymore * no future drivers using ufshcd_alloc_host() could ever forget adding the cleanup

HighCVSS 7.8 · v3.1—No exploit Fix available

Memory safety

BDU:2025-04374

Published: Feb 26, 2025
Updated: Jun 17, 2026
EPSS: 0.2% · 12th 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.2%

CISA SSVC decision

Exploitation: none
Automatable: no
Technical impact: total

Vulnrichment: CISA's decision-tree inputs.

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.12 and later · before 6.12.14
linux linux kernel6.13 and later · before 6.13.3
linux linux kernel6.14

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.12affected
- d76d9d7d1009968dd3a0fc30e5f5ee9fbffc1350 and later · before 0a6895c03b1f439236e2d22b1a69ebfc1eb9d5eaaffected · git
- d76d9d7d1009968dd3a0fc30e5f5ee9fbffc1350 and later · before d06eb2620d3bf16056b8b7ea3744dbb5e30512f4affected · git
- d76d9d7d1009968dd3a0fc30e5f5ee9fbffc1350 and later · before 0dc539b888fb5f56b6eeddd95433eab557d4b0c1affected · git
- d76d9d7d1009968dd3a0fc30e5f5ee9fbffc1350 and later · before 0c77c0d754fe83cb154715fcfec6c3faef94f207affected · git
- d76d9d7d1009968dd3a0fc30e5f5ee9fbffc1350 and later · before 9c185beae09a3eb85f54777edafa227f7e03075daffected · git
- d76d9d7d1009968dd3a0fc30e5f5ee9fbffc1350 and later · before f8fb2403ddebb5eea0033d90d9daae4c88749adaaffected · git
- before 5.12not affected · semver
- 5.15.209 and later · up to and including 5.15.*not affected · semver
- 6.1.175 and later · up to and including 6.1.*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.176-1	6.1.176-1
Debian:13	linux	before 6.12.15-1	6.12.15-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-2025-21736Feb 26, 2025 · nilfs2: fix possible int overflows in nilfs_fiemap()
22Monitor
← EarlierCVE-2025-21737Feb 26, 2025 · ceph: fix memory leak in ceph_mds_auth_match()
22Monitor
Later →CVE-2025-21741Feb 26, 2025 · usbnet: ipheth: fix DPE OoB read
28Monitor

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	0a6895c03b1f439236e2d22b1a69ebfc1eb9d5ea	Vendor (CNA)
Linux Linux	0c77c0d754fe83cb154715fcfec6c3faef94f207	Vendor (CNA)
Linux Linux	0dc539b888fb5f56b6eeddd95433eab557d4b0c1	Vendor (CNA)
Linux Linux	9c185beae09a3eb85f54777edafa227f7e03075d	Vendor (CNA)
Linux Linux	d06eb2620d3bf16056b8b7ea3744dbb5e30512f4	Vendor (CNA)
Linux Linux	f8fb2403ddebb5eea0033d90d9daae4c88749ada	Vendor (CNA)
azl3 kernel 6.6.134.1-2 on Azure Linux 3.0	6.6.137.1-2 · CBL-Mariner Releases	Microsoft (MSRC)
debian:linux	6.1.176-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-secondary

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:11 PM UTC

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

References

git.kernel.org/stable/c/0a6895c03b1f439236e2d22b1a69ebfc1eb9d5ea

Show all references (5 more)

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

All records