CVE-2025-38595: xen: fix UAF in dmabuf_exp_from_pages()
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.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 2be49867e68abbeb52d7f5d15eb1216154e2c0a0, 3edfd2353f301bfffd5ee41066e37320a59ccc2d, 532c8b51b3a8676cbf533a291f8156774f30ea87.
Low priority for now. Upgrade to Linux Linux 2be49867e68abbeb52d7f5d15eb1216154e2c0a0, 3edfd2353f301bfffd5ee41066e37320a59ccc2d, 532c8b51b3a8676cbf533a291f8156774f30ea87 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: xen: fix UAF in dmabuf_exp_from_pages() [dma_buf_fd() fixes; no preferences regarding the tree it goes through - up to xen folks] As soon as we'd inserted a file reference into descriptor table, another thread could close it. That's fine for the case when all we are doing is returning that descriptor to userland (it's a race, but it's a userland race and there's nothing the kernel can do about it). However, if we follow fd_install() with any kind of access to objects that would be destroyed on close (be it the struct file itself or anything destroyed by its ->release()), we have a UAF. dma_buf_fd() is a combination of reserving a descriptor and fd_install(). gntdev dmabuf_exp_from_pages() calls it and then proceeds to access the objects destroyed on close - starting with gntdev_dmabuf itself. Fix that by doing reserving descriptor before anything else and do fd_install() only when everything had been set up.
- Published
- Aug 19, 2025
- Updated
- Oct 30, 2026
- EPSS
- 0.2% · 12th percentile
- CWE
- CWE-416
Report tools
Action score
31
Monitor
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
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
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 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 |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel4.19 and later · before 6.12.42
- linux linux kernel6.13 and later · before 6.15.10
- linux linux kernel6.16 and later · before 6.16.1
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
- 4.19affected
- a240d6e42e28c34fdc34b3a98ca838a31c939901 and later · before 2be49867e68abbeb52d7f5d15eb1216154e2c0a0affected · git
- a240d6e42e28c34fdc34b3a98ca838a31c939901 and later · before ba8bc644f168509c16d48444991de7cfea3f12ecaffected · git
- a240d6e42e28c34fdc34b3a98ca838a31c939901 and later · before e5907885260401bba300d4d18d79875c05b82651affected · git
- a240d6e42e28c34fdc34b3a98ca838a31c939901 and later · before 3edfd2353f301bfffd5ee41066e37320a59ccc2daffected · git
- a240d6e42e28c34fdc34b3a98ca838a31c939901 and later · before d59d49af4aeed9a81e673e37c26c6a3bacf1a181affected · git
- a240d6e42e28c34fdc34b3a98ca838a31c939901 and later · before 532c8b51b3a8676cbf533a291f8156774f30ea87affected · git
- before 4.19not affected · semver
- 6.1.191 and later · up to and including 6.1.*not affected · semver
- 6.6.160 and later · up to and including 6.6.*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 | from 0 | — |
| Debian:13 | linux | before 6.12.43-1 | 6.12.43-1 |
| Debian:14 | linux | before 6.16.3-1 | 6.16.3-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-38591Aug 19, 2025 · bpf: Reject narrower access to pointer ctx fields22Monitor
- ← EarlierCVE-2025-38593Aug 19, 2025 · Bluetooth: hci_sync: fix double free in 'hci_discovery_filter_clear()'31Monitor
- Later →CVE-2025-38597Aug 19, 2025 · drm/rockchip: vop2: fail cleanly if missing a primary plane for a video-port22Monitor
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 | 2be49867e68abbeb52d7f5d15eb1216154e2c0a0 | Vendor (CNA) |
| Linux Linux | 3edfd2353f301bfffd5ee41066e37320a59ccc2d | Vendor (CNA) |
| Linux Linux | 532c8b51b3a8676cbf533a291f8156774f30ea87 | Vendor (CNA) |
| Linux Linux | ba8bc644f168509c16d48444991de7cfea3f12ec | Vendor (CNA) |
| Linux Linux | d59d49af4aeed9a81e673e37c26c6a3bacf1a181 | Vendor (CNA) |
| Linux Linux | e5907885260401bba300d4d18d79875c05b82651 | Vendor (CNA) |
| debian:linux | 6.12.43-1 · Debian:13 | 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 researchersFinders, 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 FreeCVSS 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 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
free(dev->buf);
/* ... another thread is still running ... */
process(dev->buf);Fixed
lock(&dev->lock);
free(dev->buf);
dev->buf = NULL;
unlock(&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✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- git.kernel.org/stable/c/3edfd2353f301bfffd5ee41066e37320a59ccc2d
- git.kernel.org/stable/c/532c8b51b3a8676cbf533a291f8156774f30ea87
- git.kernel.org/stable/c/ba8bc644f168509c16d48444991de7cfea3f12ec
- git.kernel.org/stable/c/d59d49af4aeed9a81e673e37c26c6a3bacf1a181
- git.kernel.org/stable/c/e5907885260401bba300d4d18d79875c05b82651
Vendor advisories and official records. Exploit/PoC links are deliberately left out.