CVE-2025-21739scsi: ufs: core: Fix use-after free in init error and remove paths
- 7.8HighCVSS base score
- 0.22%Exploitation in 30 daysEPSS · top 87% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
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
Timeline
ID reserved
By Linux
- 2 months later
· 2 months later
Published
- 15 months later
· 15 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| CISA-ADPADP (enrichment) | 3.1 | High7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVDNVD · Modified | 3.1 | High7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
- EPSS (exploitation in 30 days)
- 0.22% · top 87% of all CVEs (13 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: total
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.
Affected products
- affected d76d9d7d1009968dd3a0fc30e5f5ee9fbffc1350 – < 0a6895c03b1f439236e2d22b1a69ebfc1eb9d5ea
- affected d76d9d7d1009968dd3a0fc30e5f5ee9fbffc1350 – < d06eb2620d3bf16056b8b7ea3744dbb5e30512f4
- affected d76d9d7d1009968dd3a0fc30e5f5ee9fbffc1350 – < 0dc539b888fb5f56b6eeddd95433eab557d4b0c1
- affected d76d9d7d1009968dd3a0fc30e5f5ee9fbffc1350 – < 0c77c0d754fe83cb154715fcfec6c3faef94f207
- affected d76d9d7d1009968dd3a0fc30e5f5ee9fbffc1350 – < 9c185beae09a3eb85f54777edafa227f7e03075d
- affected d76d9d7d1009968dd3a0fc30e5f5ee9fbffc1350 – < f8fb2403ddebb5eea0033d90d9daae4c88749ada
- affected 5.12
- unaffected < 5.12
- unaffected 5.15.209 – ≤ 5.15.*
- unaffected 6.1.175 – ≤ 6.1.*
- unaffected 6.6.135 – ≤ 6.6.*
- unaffected 6.12.14 – ≤ 6.12.*
- unaffected 6.13.3 – ≤ 6.13.*
- unaffected 6.14 – ≤ *
References
References6
- https://git.kernel.org/stable/c/0a6895c03b1f439236e2d22b1a69ebfc1eb9d5ea (opens in a new tab)
- https://git.kernel.org/stable/c/d06eb2620d3bf16056b8b7ea3744dbb5e30512f4 (opens in a new tab)
- https://git.kernel.org/stable/c/0dc539b888fb5f56b6eeddd95433eab557d4b0c1 (opens in a new tab)
- https://git.kernel.org/stable/c/0c77c0d754fe83cb154715fcfec6c3faef94f207 (opens in a new tab)
- https://git.kernel.org/stable/c/9c185beae09a3eb85f54777edafa227f7e03075d (opens in a new tab)
- https://git.kernel.org/stable/c/f8fb2403ddebb5eea0033d90d9daae4c88749ada (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2025-5177 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2025-21739)Record last updated .