Fixed
Created: Nov 12, 2025
Updated: Nov 25, 2025
Resolved Date: Nov 24, 2025
Found In Version: 10.25.33.1
Fix Version: 10.25.33.3
Severity: Standard
Applicable for: Wind River Linux LTS 25
Component/s: Kernel
In the Linux kernel, the following vulnerability has been resolved:[EOL][EOL]drm/xe/guc: Check GuC running state before deregistering exec queue[EOL][EOL]In normal operation, a registered exec queue is disabled and[EOL]deregistered through the GuC, and freed only after the GuC confirms[EOL]completion. However, if the driver is forced to unbind while the exec[EOL]queue is still running, the user may call exec_destroy() after the GuC[EOL]has already been stopped and CT communication disabled.[EOL][EOL]In this case, the driver cannot receive a response from the GuC,[EOL]preventing proper cleanup of exec queue resources. Fix this by directly[EOL]releasing the resources when GuC is not running.[EOL][EOL]Here is the failure dmesg log:[EOL]"[EOL][ 468.089581] ---[ end trace 0000000000000000 ]---[EOL][ 468.089608] pci 0000:03:00.0: [drm] *ERROR* GT0: GUC ID manager unclean (1/65535)[EOL][ 468.090558] pci 0000:03:00.0: [drm] GT0: total 65535[EOL][ 468.090562] pci 0000:03:00.0: [drm] GT0: used 1[EOL][ 468.090564] pci 0000:03:00.0: [drm] GT0: range 1..1 (1)[EOL][ 468.092716] ------------[ cut here ]------------[EOL][ 468.092719] WARNING: CPU: 14 PID: 4775 at drivers/gpu/drm/xe/xe_ttm_vram_mgr.c:298 ttm_vram_mgr_fini+0xf8/0x130 [xe][EOL]"[EOL][EOL]v2: use xe_uc_fw_is_running() instead of xe_guc_ct_enabled().[EOL] As CT may go down and come back during VF migration.[EOL][EOL](cherry picked from commit 9b42321a02c50a12b2beb6ae9469606257fbecea)
