GPU VulnDB

Database/NVIDIA / GPU stack

Linux kernel drm/xe GuC: async exec queue destruction can deadlock drmm cleanup on device removal

CVSS 7.8CVE-2026-68382NVIDIA / GPU stackcurated

Impact

GuC exec queue destruction runs asynchronously; if the final device put happens from the destroy worker, drmm cleanup drains the same workqueue and deadlocks. The practical exposure is a hung PCI remove or driver unbind on an Intel Xe host - a GPU node that will not release the device and in most cases has to be rebooted rather than recovered. This is an availability and maintainability problem on the fleet, not a tenant isolation break; nothing in the record indicates a memory-disclosure or escalation path despite the high CVSS attached to the kernel CNA's default scoring.

Who can reach it

Local and administrative: reached through device unbind, hot-unplug, or driver rebind while queue destroy work is pending. Not reachable by an unprivileged tenant on its own.

What to do

Apply the stable fix that holds a drm_device reference for the queue lifetime and moves destroy work to a module-lifetime workqueue flushed on PCI remove; reboot the node to pick it up. Until then, treat xe driver unbind/rebind as an operation that may require a reboot to clear.

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.