GPU VulnDB

Database/NVIDIA / GPU stack

Linux kernel drm/xe: unreset current_op on vm_bind retry overflows the page-table op array

CVSS 7.8CVE-2026-68264NVIDIA / GPU stackcurated

Impact

On Intel Xe GPUs (including Data Center GPU Max parts), xe_pt_update_ops_init() does not reset current_op, so each retry of the vm_bind preparation loop - triggered by lock contention or OOM eviction, both routine on a loaded multi-tenant node - keeps incrementing the index past the array allocated by xe_vma_ops_alloc(). The result is an out-of-bounds write into SLUB memory followed by a use-after-free in xe_migrate_update_pgtables_cpu(). Any local process holding a render node can drive vm_bind and provoke the retry path, which makes this a plausible local privilege-escalation primitive on a shared GPU node rather than a mere crash.

Who can reach it

Local user with access to the Xe DRM render node (any tenant with an Intel GPU workload container). No special privilege beyond opening the device; no remote path.

What to do

Take the stable kernel fix for your series and reboot the node. There is no module-reload workaround that is safe here - the bug lives in the memory manager of the live driver - so plan a drain and reboot per affected host.

References

Related entries

All NVIDIA / GPU stack entries

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.