CVEvulnerability
CVE-2025-38703
7.8 HIGH
Official page ↗
- Status
- Modified
- Published
- 2025-09-04
- Last modified
- 2026-10-19
- Assigner
- 416baaa9-dc9f-4396-8d5f-8c081fb06d67
- CVSS 3.1 (416baaa9-dc9f-4396-8d5f-8c081fb06d67)
- 7.8 HIGH — CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- CVSS 3.1 ([email protected])
- 7.8 HIGH — CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- Weaknesses
- CWE-416
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.
Affected configurations
• linux linux kernel (>= 6.8 < 6.12.43)
• linux linux kernel (>= 6.13 < 6.15.11)
• linux linux kernel (>= 6.16 < 6.16.2)
Related
Weakness · CWE (1)
- CWE-416 Use After Free weakness
References
- https://git.kernel.org/stable/c/683b0e397dad9f26a42dcacf6f7f545a77ce6c06 Patch
- https://git.kernel.org/stable/c/6bd90e700b4285e6a7541e00f969cab0d696adde Patch
- https://git.kernel.org/stable/c/b17fcce70733c211cb5dabf54f4f9491920b1d92 Patch
- https://git.kernel.org/stable/c/ba37807d08bae67de6139346a85650cab5f6145a Patch