CVE-2025-38011: drm/amdgpu: csa unmap use uninterruptible lock
Noroxi assessment
Priority: Monitor (action score 22/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.21% (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 8d2979b9bb1be0f4a52dff600e56d780403e04ac, 8d71c3231b33e24a911b8f2d8c3a17ee40aa32d5, a0fa7873f2f869087b1e7793f7fac3713a1e3afe.
Low priority for now. Upgrade to Linux Linux 8d2979b9bb1be0f4a52dff600e56d780403e04ac, 8d71c3231b33e24a911b8f2d8c3a17ee40aa32d5, a0fa7873f2f869087b1e7793f7fac3713a1e3afe 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: drm/amdgpu: csa unmap use uninterruptible lock After process exit to unmap csa and free GPU vm, if signal is accepted and then waiting to take vm lock is interrupted and return, it causes memory leaking and below warning backtrace. Change to use uninterruptible wait lock fix the issue. WARNING: CPU: 69 PID: 167800 at amd/amdgpu/amdgpu_kms.c:1525 amdgpu_driver_postclose_kms+0x294/0x2a0 [amdgpu] Call Trace: <TASK> drm_file_free.part.0+0x1da/0x230 [drm] drm_close_helper.isra.0+0x65/0x70 [drm] drm_release+0x6a/0x120 [drm] amdgpu_drm_release+0x51/0x60 [amdgpu] __fput+0x9f/0x280 ____fput+0xe/0x20 task_work_run+0x67/0xa0 do_exit+0x217/0x3c0 do_group_exit+0x3b/0xb0 get_signal+0x14a/0x8d0 arch_do_signal_or_restart+0xde/0x100 exit_to_user_mode_loop+0xc1/0x1a0 exit_to_user_mode_prepare+0xf4/0x100 syscall_exit_to_user_mode+0x17/0x40 do_syscall_64+0x69/0xc0 (cherry picked from commit 7dbbfb3c171a6f63b01165958629c9c26abf38ab)
- Published
- Jun 18, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 11th percentile
- CWE
- CWE-401
Report tools
Action score
22
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
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.
Is your version affected? Check itNoroxi 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 helpAffected 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 |
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
- 6.6affected
- 8a206685d36f6f0c6b72637f920ef973ea9cc936 and later · before 8d2979b9bb1be0f4a52dff600e56d780403e04acaffected · git
- 8a206685d36f6f0c6b72637f920ef973ea9cc936 and later · before 8d71c3231b33e24a911b8f2d8c3a17ee40aa32d5affected · git
- 8a206685d36f6f0c6b72637f920ef973ea9cc936 and later · before a1adc8d9a0d219d4e88672c30dbc9ea960d73136affected · git
- 8a206685d36f6f0c6b72637f920ef973ea9cc936 and later · before a0fa7873f2f869087b1e7793f7fac3713a1e3afeaffected · git
- before 6.6not affected · semver
- 6.6.122 and later · up to and including 6.6.*not affected · semver
- 6.12.30 and later · up to and including 6.12.*not affected · semver
- 6.14.8 and later · up to and including 6.14.*not affected · semver
- 6.15 and laternot affected · original_commit_for_fix
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel6.6 and later · before 6.12.30
- linux linux kernel6.13 and later · before 6.14.8
- linux linux kernel6.15
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:13 | linux | before 6.12.30-1 | 6.12.30-1 |
| openSUSE:Tumbleweed | kernel-source | before 6.16.9-1.1 | 6.16.9-1.1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- 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…KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2025-38007Jun 18, 2025 · HID: uclogic: Add NULL check in uclogic_input_configured()22Monitor
- ← EarlierCVE-2025-38008Jun 18, 2025 · mm/page_alloc: fix race condition in unaccepted memory handling18Monitor
- Later →CVE-2025-38012Jun 18, 2025 · sched_ext: bpf_iter_scx_dsq_new() should always initialize iterator22Monitor
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 | 8d2979b9bb1be0f4a52dff600e56d780403e04ac | Vendor (CNA) |
| Linux Linux | 8d71c3231b33e24a911b8f2d8c3a17ee40aa32d5 | Vendor (CNA) |
| Linux Linux | a0fa7873f2f869087b1e7793f7fac3713a1e3afe | Vendor (CNA) |
| Linux Linux | a1adc8d9a0d219d4e88672c30dbc9ea960d73136 | Vendor (CNA) |
| debian:linux | 6.12.30-1 · Debian:13 | Package registry (OSV) |
| opensuse:kernel-source | 6.16.9-1.1 · openSUSE:Tumbleweed | 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.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
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
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-401 · Missing Release of Memory after Effective LifetimeCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
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 (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.