CVE-2025-40166

Technical Description

In the Linux kernel, the following vulnerability has been resolved:

drm/xe/guc: Check GuC running state before deregistering exec queue

In normal operation, a registered exec queue is disabled and

deregistered through the GuC, and freed only after the GuC confirms

completion. However, if the driver is forced to unbind while the exec

queue is still running, the user may call exec_destroy() after the GuC

has already been stopped and CT communication disabled.

In this case, the driver cannot receive a response from the GuC,

preventing proper cleanup of exec queue resources. Fix this by directly

releasing the resources when GuC is not running.

Here is the failure dmesg log:

"

[ 468.089581] ---[ end trace 0000000000000000 ]---

[ 468.089608] pci 0000:03:00.0: [drm] *ERROR* GT0: GUC ID manager unclean (1/65535)

[ 468.090558] pci 0000:03:00.0: [drm] GT0: total 65535

[ 468.090562] pci 0000:03:00.0: [drm] GT0: used 1

[ 468.090564] pci 0000:03:00.0: [drm] GT0: range 1..1 (1)

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

References