CVE-2025-40166
BaseFortify
Publication date: 2025-11-12
Last updated on: 2025-11-12
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | * |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-UNKNOWN |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability occurs in the Linux kernel's graphics driver related to the GuC (Graphics microcontroller) execution queue management. Normally, when an exec queue is deregistered, the GuC confirms completion before resources are freed. However, if the driver is forced to unbind while the exec queue is still running and the GuC has already stopped, the driver cannot receive a response to properly clean up resources. This leads to improper cleanup of exec queue resources, potentially causing errors or resource leaks. The fix involves checking if the GuC is running before deregistering and directly releasing resources if it is not.
How can this vulnerability impact me? :
This vulnerability can cause improper cleanup of graphics execution queue resources in the Linux kernel, which may lead to errors, resource leaks, or instability in the graphics subsystem. This could affect system performance or reliability, especially in environments relying on GPU operations managed by the affected driver.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by monitoring the system logs for specific error messages related to the GuC exec queue deregistration failure. Look for dmesg logs containing errors such as '*ERROR* GT0: GUC ID manager unclean' and warnings from the drm/xe driver, for example: sudo dmesg | grep -i 'GUC ID manager unclean' sudo dmesg | grep -i 'ttm_vram_mgr_fini' These commands help identify if the driver is encountering the described issue during exec queue cleanup.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation involves updating the Linux kernel to a version that includes the fix for this vulnerability, which ensures that the driver checks the GuC running state before deregistering the exec queue and properly releases resources when GuC is not running. Until the update is applied, avoid forcing driver unbinds while exec queues are running to prevent improper cleanup and potential errors.