GPU VulnDB

Database/NVIDIA / GPU stack

Linux kernel drm/xe VF: CCS batch buffers attached/detached without waiting for in-flight BO copy

CVSS 7.8CVE-2026-68384NVIDIA / GPU stackcurated

Impact

On Intel Xe GPUs used in SR-IOV mode, xe_bo_move() attached the VF compression (CCS) read/write batch buffers after submitting the copy job and detached them before the blit had signalled. A VF migration event that pauses the guest mid-copy can therefore observe partially copied CCS metadata with no attach state, or race the save/restore path against a still-running blit whose batch buffers have already been torn down. On a node where GPU partitions are handed to separate tenants, this is memory-state corruption around a tenant boundary during live migration, with memory corruption or a GPU/driver crash as the realistic outcome. The same commit also fixes xe_sriov_vf_ccs_attach_bo() silently discarding per-context attach failures.

Who can reach it

Local, on a host running drm/xe with SR-IOV virtual functions. No remote path: triggering requires driving GPU buffer-object moves while a VF migration event occurs. A tenant holding an Xe VF can generate the BO traffic; the migration event itself is operator-initiated.

What to do

Take the stable kernel fix (commits in the record) and reboot each affected GPU node; there is no module-reload path for a driver bound to live GPU workloads. Nodes that do not enable Xe SR-IOV VFs are not affected and can be patched on the normal cycle.

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.