CVE-2025-38703drm/xe: Make dma-fences compliant with the safe access rules
- 7.8HighCVSS base score
- 0.18%Exploitation in 30 daysEPSS · top 93% 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: 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.
Timeline
ID reserved
By Linux
- 5 months later
· 5 months later
Published
- 11 months later
· 11 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 |
|---|---|---|---|
| LinuxCNA (assigner) | 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.18% · top 93% of all CVEs (15 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.
Affected products
- affected dd08ebf6c3525a7ea2186e636df064ea47281987 – < b17fcce70733c211cb5dabf54f4f9491920b1d92
- affected dd08ebf6c3525a7ea2186e636df064ea47281987 – < ba37807d08bae67de6139346a85650cab5f6145a
- affected dd08ebf6c3525a7ea2186e636df064ea47281987 – < 683b0e397dad9f26a42dcacf6f7f545a77ce6c06
- affected dd08ebf6c3525a7ea2186e636df064ea47281987 – < 6bd90e700b4285e6a7541e00f969cab0d696adde
- affected 6.8
- unaffected < 6.8
- unaffected 6.12.43 – ≤ 6.12.*
- unaffected 6.15.11 – ≤ 6.15.*
- unaffected 6.16.2 – ≤ 6.16.*
- unaffected 6.17 – ≤ *
References
References4
- https://git.kernel.org/stable/c/b17fcce70733c211cb5dabf54f4f9491920b1d92 (opens in a new tab)
- https://git.kernel.org/stable/c/ba37807d08bae67de6139346a85650cab5f6145a (opens in a new tab)
- https://git.kernel.org/stable/c/683b0e397dad9f26a42dcacf6f7f545a77ce6c06 (opens in a new tab)
- https://git.kernel.org/stable/c/6bd90e700b4285e6a7541e00f969cab0d696adde (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-26766 (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-38703)Record last updated .