CVE-2025-38703: drm/xe: Make dma-fences compliant with the safe access rules
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.16% (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 683b0e397dad9f26a42dcacf6f7f545a77ce6c06, 6bd90e700b4285e6a7541e00f969cab0d696adde, b17fcce70733c211cb5dabf54f4f9491920b1d92.
Low priority for now. Upgrade to Linux Linux 683b0e397dad9f26a42dcacf6f7f545a77ce6c06, 6bd90e700b4285e6a7541e00f969cab0d696adde, b17fcce70733c211cb5dabf54f4f9491920b1d92 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/xe: Make dma-fences compliant with the safe access rules Xe can free some of the data pointed to by the dma-fences it exports. Most notably the timeline name can get freed if userspace closes the associated submit queue. At the same time the fence could have been exported to a third party (for example a sync_fence fd) which will then cause an use- after-free on subsequent access. To make this safe we need to make the driver compliant with the newly documented dma-fence rules. Driver has to ensure a RCU grace period between signalling a fence and freeing any data pointed to by said fence. For the timeline name we simply make the queue be freed via kfree_rcu and for the shared lock associated with multiple queues we add a RCU grace period before freeing the per GT structure holding the lock.
- Published
- Sep 4, 2025
- Updated
- Oct 19, 2026
- EPSS
- 0.1% · 6th 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.1%
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 kernel6.8 and later · before 6.12.43
- linux linux kernel6.13 and later · before 6.15.11
- linux linux kernel6.16 and later · before 6.16.2
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.8affected
- dd08ebf6c3525a7ea2186e636df064ea47281987 and later · before b17fcce70733c211cb5dabf54f4f9491920b1d92affected · git
- dd08ebf6c3525a7ea2186e636df064ea47281987 and later · before ba37807d08bae67de6139346a85650cab5f6145aaffected · git
- dd08ebf6c3525a7ea2186e636df064ea47281987 and later · before 683b0e397dad9f26a42dcacf6f7f545a77ce6c06affected · git
- dd08ebf6c3525a7ea2186e636df064ea47281987 and later · before 6bd90e700b4285e6a7541e00f969cab0d696addeaffected · git
- before 6.8not affected · semver
- 6.12.43 and later · up to and including 6.12.*not affected · semver
- 6.15.11 and later · up to and including 6.15.*not affected · semver
- 6.16.2 and later · up to and including 6.16.*not affected · semver
- 6.17 and laternot affected · original_commit_for_fix
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:10 | kernel-abi-stablelists | before 6.12.0-124.43.1.el10_1 | 6.12.0-124.43.1.el10_1 |
| AlmaLinux:10 | kernel-doc | before 6.12.0-124.43.1.el10_1 | 6.12.0-124.43.1.el10_1 |
| AlmaLinux:9 | kernel | before 5.14.0-611.24.1.el9_7 | 5.14.0-611.24.1.el9_7 |
| AlmaLinux:9 | kernel-64k | before 5.14.0-611.24.1.el9_7 | 5.14.0-611.24.1.el9_7 |
| AlmaLinux:9 | kernel-64k-core | before 5.14.0-611.24.1.el9_7 | 5.14.0-611.24.1.el9_7 |
| AlmaLinux:9 | kernel-64k-debug | before 5.14.0-611.24.1.el9_7 | 5.14.0-611.24.1.el9_7 |
| AlmaLinux:9 | kernel-64k-debug-core | before 5.14.0-611.24.1.el9_7 | 5.14.0-611.24.1.el9_7 |
| AlmaLinux:9 | kernel-64k-debug-devel | before 5.14.0-611.24.1.el9_7 | 5.14.0-611.24.1.el9_7 |
| AlmaLinux:9 | kernel-64k-debug-devel-matched | before 5.14.0-611.24.1.el9_7 | 5.14.0-611.24.1.el9_7 |
| AlmaLinux:9 | kernel-64k-debug-modules | before 5.14.0-611.24.1.el9_7 | 5.14.0-611.24.1.el9_7 |
| AlmaLinux:9 | kernel-64k-debug-modules-core | before 5.14.0-611.24.1.el9_7 | 5.14.0-611.24.1.el9_7 |
| AlmaLinux:9 | kernel-64k-debug-modules-extra | before 5.14.0-611.24.1.el9_7 | 5.14.0-611.24.1.el9_7 |
| AlmaLinux:9 | kernel-64k-devel | before 5.14.0-611.24.1.el9_7 | 5.14.0-611.24.1.el9_7 |
| AlmaLinux:9 | kernel-64k-devel-matched | before 5.14.0-611.24.1.el9_7 | 5.14.0-611.24.1.el9_7 |
| AlmaLinux:9 | kernel-64k-modules | before 5.14.0-611.24.1.el9_7 | 5.14.0-611.24.1.el9_7 |
| AlmaLinux:9 | kernel-64k-modules-core | before 5.14.0-611.24.1.el9_7 | 5.14.0-611.24.1.el9_7 |
| AlmaLinux:9 | kernel-64k-modules-extra | before 5.14.0-611.24.1.el9_7 | 5.14.0-611.24.1.el9_7 |
| AlmaLinux:9 | kernel-abi-stablelists | before 5.14.0-611.24.1.el9_7 | 5.14.0-611.24.1.el9_7 |
| AlmaLinux:9 | kernel-core | before 5.14.0-611.24.1.el9_7 | 5.14.0-611.24.1.el9_7 |
| AlmaLinux:9 | kernel-cross-headers | before 5.14.0-611.24.1.el9_7 | 5.14.0-611.24.1.el9_7 |
| AlmaLinux:9 | kernel-debug | before 5.14.0-611.24.1.el9_7 | 5.14.0-611.24.1.el9_7 |
| AlmaLinux:9 | kernel-debug-core | before 5.14.0-611.24.1.el9_7 | 5.14.0-611.24.1.el9_7 |
| AlmaLinux:9 | kernel-debug-devel | before 5.14.0-611.24.1.el9_7 | 5.14.0-611.24.1.el9_7 |
| AlmaLinux:9 | kernel-debug-devel-matched | before 5.14.0-611.24.1.el9_7 | 5.14.0-611.24.1.el9_7 |
+96
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-38701Sep 4, 2025 · ext4: do not BUG when INLINE_DATA_FL lacks system.data xattr22Monitor
- ← EarlierCVE-2025-38702Sep 4, 2025 · fbdev: fix potential buffer overflow in do_register_framebuffer()31Monitor
- Later →CVE-2025-38704Sep 4, 2025 · rcu/nocb: Fix possible invalid rdp's->nocb_cb_kthread pointer access31Monitor
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 | 683b0e397dad9f26a42dcacf6f7f545a77ce6c06 | Vendor (CNA) |
| Linux Linux | 6bd90e700b4285e6a7541e00f969cab0d696adde | Vendor (CNA) |
| Linux Linux | b17fcce70733c211cb5dabf54f4f9491920b1d92 | Vendor (CNA) |
| Linux Linux | ba37807d08bae67de6139346a85650cab5f6145a | Vendor (CNA) |
| almalinux:kernel | 5.14.0-611.24.1.el9_7 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k | 5.14.0-611.24.1.el9_7 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-core | 5.14.0-611.24.1.el9_7 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug | 5.14.0-611.24.1.el9_7 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-core | 5.14.0-611.24.1.el9_7 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-devel | 5.14.0-611.24.1.el9_7 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-devel-matched | 5.14.0-611.24.1.el9_7 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules | 5.14.0-611.24.1.el9_7 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules-core | 5.14.0-611.24.1.el9_7 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules-extra | 5.14.0-611.24.1.el9_7 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-devel | 5.14.0-611.24.1.el9_7 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-devel-matched | 5.14.0-611.24.1.el9_7 · AlmaLinux:9 | Package registry (OSV) |
| debian:linux | 6.12.43-1 · Debian:13 | Package registry (OSV) |
| red hat:kernel-64k-debug-debuginfo | 0:5.14.0-611.24.1.el9_7 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-64k-debug-devel | 0:5.14.0-611.24.1.el9_7 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-64k-debug-devel-matched | 0:5.14.0-611.24.1.el9_7 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-64k-debuginfo | 0:5.14.0-611.24.1.el9_7 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-64k-devel | 0:5.14.0-611.24.1.el9_7 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-64k-devel-matched | 0:5.14.0-611.24.1.el9_7 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-debug-debuginfo | 0:5.14.0-611.24.1.el9_7 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-debug-devel | 0:5.14.0-611.24.1.el9_7 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-debug-devel-matched | 0:5.14.0-611.24.1.el9_7 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-debuginfo | 0:5.14.0-611.24.1.el9_7 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-debuginfo-common-aarch64 | 0:5.14.0-611.24.1.el9_7 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-debuginfo-common-ppc64le | 0:5.14.0-611.24.1.el9_7 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| rocky linux:kernel | 0:5.14.0-611.24.1.el9_7 · Rocky Linux:9 | 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 (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.