Database/Kernel, userspace & hypervisor
Linux kernel (drivers/gpu/drm/xe): A tenant that submits a deliberately malformed array bind to the Xe VM_BIND ioctl
Impact
A tenant that submits a deliberately malformed array bind to the Xe VM_BIND ioctl gets the driver to free the same kernel allocation twice, which is a slab-corruption primitive rather than a clean error return. On a shared Intel GPU node that is the classic path from an unprivileged container to kernel memory corruption and privilege escalation, or at minimum a panic that takes every co-tenant on the box down with it.
Who can reach it
Directly reachable from any container holding /dev/dri/renderD* on a host running the Intel Xe driver - no card* node, no DRM master, no display access required. The attacker just calls DRM_IOCTL_XE_VM_BIND with an array of bind ops whose argument validation fails; the failure path is the bug.
What to do
Boot a kernel carrying the fix commits below. Until then, remove /dev/dri/renderD* from any container that does not genuinely need GPU access, and treat nodes running the xe driver with untrusted tenants as exposed - there is no runtime toggle that disables VM_BIND while keeping the GPU usable.
References
Related entries
- Linux kernel (drivers/gpu/drm/xe): On the migration error path the previous fence is released before the code waits onCVE-2025-39740 · Linux kernel (drivers/gpu/drm/xe)High
- Linux kernel (drivers/gpu/drm/xe): The observation-config ioctl dereferences the config object after releasing the lockCVE-2025-71099 · Linux kernel (drivers/gpu/drm/xe)High
- Linux kernel (drivers/gpu/drm/xe): The Xe userptr path takes folio locks while holding the MMU notifier lock, whichCVE-2025-37868 · Linux kernel (drivers/gpu/drm/xe)Medium
- Linux kernel (drivers/gpu/drm/xe): A batched array of VM_BIND operations could evict other buffer objects belonging toCVE-2025-40086 · Linux kernel (drivers/gpu/drm/xe)Medium
- Linux kernel (drivers/gpu/drm/xe): A tenant's jobs can occupy the same copy engines the driver needs to service GPUCVE-2024-37026 · Linux kernel (drivers/gpu/drm/xe)Medium
- Linux kernel (drivers/gpu/drm/xe): Same per-client accounting path, different failure - if the fdinfo read drops theCVE-2024-46867 · Linux kernel (drivers/gpu/drm/xe)Medium
This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.