Vulnerability · CVE-2025-38517
In the Linux kernel, the following vulnerability has been resolved: lib/alloc_tag: do not acquire non-existent lock in alloc_tag_top_users() alloc_tag_top_users() attempts to lock
Published Aug 16, 2025 · catalog updated May 11, 2026 · Linux Linux
Check this week
CVE-2025-38517 is not in CISA KEV. FIRST estimates a 15.00% chance of exploitation in the next 30 days. Check whether you run Linux Linux.
Gaps on this record
- No vendor fix or required action is stored. Compare the linked advisory before you change production.
- Severity
- None0.0
- Known exploitation
- Not in CISA/VulnCheck KEV
- EPSS
- 15.00%
- Remediation
- Version ranges on file
- Affected products
- vendor Linux Linux 1438d349d16b78d88f9e978a4a5496f078c8191b <22bf79c0c2301b6e15a688220284b147774d277e
In the Linux kernel, the following vulnerability has been resolved: lib/alloc_tag: do not acquire non-existent lock in alloc_tag_top_users() alloc_tag_top_users() attempts to lock alloc_tag_cttype->mod_lock even when the alloc_tag_cttype is not allocated because: 1) alloc tagging is disabled because mem profiling is disabled (!alloc_tag_cttype) 2) alloc tagging is enabled, but not yet initialized (!alloc_tag_cttype) 3) alloc tagging is enabled, but failed initialization (!alloc_tag_cttype or IS_ERR(alloc_tag_cttype)) In all cases, alloc_tag_cttype is not allocated, and therefore alloc_tag_top_
Are you affected?
Enter the version you run. The result uses only the ranges stored on this record.
The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.
- vendor Linux Linux 1438d349d16b78d88f9e978a4a5496f078c8191b <22bf79c0c2301b6e15a688220284b147774d277e1438d349d16b78d88f9e978a4a5496f078c8191b <22bf79c0c2301b6e15a688220284b147774d277e
How to fix CVE-2025-38517
Recommended remediation
Affected version ranges suggest a fixed boundary. Verify against the vendor advisory for your release.
Official advisories
What to do
Three questions, each answered from this record only. Confirm the vendor advisory before you patch.
Should you patch?
CVE-2025-38517 is not in CISA KEV. FIRST estimates a 15.00% chance of exploitation in the next 30 days. Check whether you run Linux Linux.
Which versions are affected?
Compare what you have installed with Linux Linux 1438d349d16b78d88f9e978a4a5496f078c8191b <22bf79c0c2301b6e15a688220284b147774d277e 1438d349d16b78d88f9e978a4a5496f078c8191b <22bf79c0c2301b6e15a688220284b147774d277e. Compare the installed version with the linked vendor advisory before you change production.
What should an analyst verify?
No weakness class is stored. EPSS 15.00%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.
Code
The project this record applies to. Exploit listings stay in References.
Timeline
Detection, updates, and resolution for this record.
Aug 16, 2025 · EUVD
Detected
In the Linux kernel, the following vulnerability has been resolved: lib/alloc_tag: do not acquire non-existent lock in alloc_tag_top_users() alloc_tag_top_users() attempts to lock alloc_tag_cttype->mod_lock even when the alloc_tag_cttype is not allocated because: 1) alloc tagging is disabled because mem profiling is disabled (!alloc_tag_cttype) 2) alloc tagging is enabled, but not yet initialized
May 11, 2026 · EUVD
Updated
In the Linux kernel, the following vulnerability has been resolved: lib/alloc_tag: do not acquire non-existent lock in alloc_tag_top_users() alloc_tag_top_users() attempts to lock alloc_tag_cttype->mod_lock even when the alloc_tag_cttype is not allocated because: 1) alloc tagging is disabled because mem profiling is disabled (!alloc_tag_cttype) 2) alloc tagging is enabled, but not yet initialized
Sources
- CVE.orgVulnerability recordCVE-2025-38517
Official CVE identifier
cve.org - EUVDVulnerability recordEUVD-2025-25081
In the Linux kernel, the following vulnerability has been resolved: lib/alloc_tag: do not acquire non-existent lock in alloc_tag_top_users() alloc_tag_top_users() attempts to lock alloc_tag_cttype->mod_lock even when the alloc_tag_cttype is not allocated because: 1) alloc tagging
euvd.enisa.europa.eu
References
Freshness
Last verified in this catalog May 11, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.