GPU VulnDB

Database/NVIDIA / GPU stack

Linux kernel drm/xe GuC: scheduler keeps a pointer to the exec queue name freed with the queue

CVSS 7.8CVE-2026-68383NVIDIA / GPU stackcurated

Impact

The GPU scheduler holds a pointer to the timeline name, but that string is freed together with the exec queue while scheduler fences can still reference it. Any consumer that reads the fence timeline name - dma-fence debugging, tracing, or sysfs/debugfs fence dumps - can touch freed memory after a queue teardown. Exec queue creation and destruction is driven by ordinary GPU clients, so the free happens on the normal path rather than only in an error case. The record describes a use-after-free read; it does not establish a write primitive.

Who can reach it

Local user with an Xe render node who can create and destroy exec queues. Observation of the stale name requires a path that prints fence timeline names.

What to do

Apply the stable fix that stores the name in struct xe_guc_exec_queue so it shares the scheduler's RCU-deferred lifetime, then reboot the node.

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.