{"dataType":"CVE_RECORD","dataVersion":"5.2","cveMetadata":{"cveId":"CVE-2025-38703","assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","state":"PUBLISHED","assignerShortName":"Linux","dateReserved":"2025-04-16T04:51:24.032Z","datePublished":"2025-09-04T15:32:54.779Z","dateUpdated":"2026-08-05T12:04:07.308Z"},"containers":{"cna":{"providerMetadata":{"orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux","dateUpdated":"2026-08-05T12:04:07.308Z"},"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/xe: Make dma-fences compliant with the safe access rules\n\nXe can free some of the data pointed to by the dma-fences it exports. Most\nnotably the timeline name can get freed if userspace closes the associated\nsubmit queue. At the same time the fence could have been exported to a\nthird party (for example a sync_fence fd) which will then cause an use-\nafter-free on subsequent access.\n\nTo make this safe we need to make the driver compliant with the newly\ndocumented dma-fence rules. Driver has to ensure a RCU grace period\nbetween signalling a fence and freeing any data pointed to by said fence.\n\nFor the timeline name we simply make the queue be freed via kfree_rcu and\nfor the shared lock associated with multiple queues we add a RCU grace\nperiod before freeing the per GT structure holding the lock."}],"metrics":[{"cvssV3_1":{"version":"3.1","vectorString":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","baseScore":7.8,"baseSeverity":"HIGH"},"scenarios":[{"lang":"en","value":"AV:L - The attack requires ioctls on the local DRM render node (`/dev/dri/renderD128`) plus a sync_file fd; there is no remote or adjacent-network path to the xe exec-queue lifecycle.\nAC:L - No race is involved — once `kfree(ge)` runs the dangling `fence->sched` pointer is permanently stale, so the attacker controls every step (create queue, export sync_file, destroy queue, spray the slab at leisure, then read) and can retry indefinitely.\nPR:L - All required ioctls (XE_EXEC_QUEUE_CREATE/DESTROY, XE_EXEC, SYNCOBJ_EXPORT_SYNC_FILE, SYNC_IOC_FILE_INFO) are `DRM_RENDER_ALLOW` with no `DRM_AUTH` or capability check, so any local user with render-node access — the default for logged-in desktop users, Android/ChromeOS apps, and GPU-passthrough containers — can exploit it.\nUI:N - The attacker performs the entire sequence within its own process using its own exec queue and its own exported fence; no victim action is needed.\nS:U - The use-after-free occurs in kernel slab memory and the impact stays within the kernel's security authority — no VM, IOMMU, or hypervisor boundary is crossed.\nC:H - `sync_fill_fence_info()` `strscpy()`s from the UAF-derived `name` pointer into `info->obj_name` and copies it to userspace, so after heap-spraying the freed `xe_guc_exec_queue` slot the attacker controls that pointer and obtains a repeatable arbitrary kernel-memory read primitive.\nI:H - This is a use-after-free of a slab object whose contents the attacker can groom, and the companion `fence->lock` defect makes `spin_lock()` write into the freed `struct xe_gt`, giving corruption of reallocated kernel objects that is leverageable for control-flow hijack.\nA:H - Dereferencing the stale `fence->sched` and the resulting wild `name` pointer readily oopses the kernel, and locking a freed `fence->lock` corrupts or deadlocks unrelated allocations, each producing a full system crash."}]}],"affected":[{"product":"Linux","vendor":"Linux","defaultStatus":"unaffected","repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","programFiles":["drivers/gpu/drm/xe/xe_guc_exec_queue_types.h","drivers/gpu/drm/xe/xe_guc_submit.c","drivers/gpu/drm/xe/xe_hw_fence.c"],"versions":[{"version":"dd08ebf6c3525a7ea2186e636df064ea47281987","lessThan":"b17fcce70733c211cb5dabf54f4f9491920b1d92","status":"affected","versionType":"git"},{"version":"dd08ebf6c3525a7ea2186e636df064ea47281987","lessThan":"ba37807d08bae67de6139346a85650cab5f6145a","status":"affected","versionType":"git"},{"version":"dd08ebf6c3525a7ea2186e636df064ea47281987","lessThan":"683b0e397dad9f26a42dcacf6f7f545a77ce6c06","status":"affected","versionType":"git"},{"version":"dd08ebf6c3525a7ea2186e636df064ea47281987","lessThan":"6bd90e700b4285e6a7541e00f969cab0d696adde","status":"affected","versionType":"git"}]},{"product":"Linux","vendor":"Linux","defaultStatus":"affected","repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","programFiles":["drivers/gpu/drm/xe/xe_guc_exec_queue_types.h","drivers/gpu/drm/xe/xe_guc_submit.c","drivers/gpu/drm/xe/xe_hw_fence.c"],"versions":[{"version":"6.8","status":"affected"},{"version":"0","lessThan":"6.8","status":"unaffected","versionType":"semver"},{"version":"6.12.43","lessThanOrEqual":"6.12.*","status":"unaffected","versionType":"semver"},{"version":"6.15.11","lessThanOrEqual":"6.15.*","status":"unaffected","versionType":"semver"},{"version":"6.16.2","lessThanOrEqual":"6.16.*","status":"unaffected","versionType":"semver"},{"version":"6.17","lessThanOrEqual":"*","status":"unaffected","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"operator":"OR","negate":false,"cpeMatch":[{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"6.8","versionEndExcluding":"6.12.43"},{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"6.8","versionEndExcluding":"6.15.11"},{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"6.8","versionEndExcluding":"6.16.2"},{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"6.8","versionEndExcluding":"6.17"}]}]}],"references":[{"url":"https://git.kernel.org/stable/c/b17fcce70733c211cb5dabf54f4f9491920b1d92"},{"url":"https://git.kernel.org/stable/c/ba37807d08bae67de6139346a85650cab5f6145a"},{"url":"https://git.kernel.org/stable/c/683b0e397dad9f26a42dcacf6f7f545a77ce6c06"},{"url":"https://git.kernel.org/stable/c/6bd90e700b4285e6a7541e00f969cab0d696adde"}],"title":"drm/xe: Make dma-fences compliant with the safe access rules","x_generator":{"engine":"bippy-1.2.0"}}}}