Linux kernel (drivers/gpu/drm/xe): A batched array of VM_BIND operations could evict other buffer objects belonging to

Impact

A batched array of VM_BIND operations could evict other buffer objects belonging to the same VM while that VM's bind pipeline is still walking them, leaving the pipeline dereferencing objects with no backing resource. A tenant can crash the kernel from an ordinary GPU address-space bind, and the crash lands inside the shared xe bind machinery on the node.

Who can reach it

A tenant container holding /dev/dri/renderD* on an Intel xe GPU submits an array of VM_BIND operations sized to force eviction inside its own VM - no privilege beyond the render node, no display path, no host root. The fallout is a kernel oops on a node other tenants are sharing.

What to do

Boot a kernel carrying the xe_vm eviction-policy fix below. Interim: cap per-tenant VRAM so binds do not push the VM into eviction, and keep panic_on_oops off so a single tenant's oops does not take the whole node with it.

References