In the Linux kernel, the following vulnerability has been resolved: drm/xe/guc: Check GuC running state before deregistering exec queue In normal… (CVE-2025-40166)
A vulnerability in the Linux kernel's drm/xe/guc driver was resolved that could lead to improper cleanup of exec queue resources if the driver is forced to unbind while the exec queue is still running. This occurs because the driver may attempt to deregister an exec queue after the GuC (Graphics microcontroller) has stopped and communication is disabled, preventing proper resource cleanup and causing errors. The fix ensures resources are released directly when the GuC is not running.
AI Analysis
Technical Summary
The vulnerability in the Linux kernel drm/xe/guc component involves the deregistration of exec queues without verifying the GuC running state. Normally, exec queues are deregistered only after GuC confirms completion. However, if the driver unbinds while the exec queue is active and GuC communication is disabled, the driver cannot receive responses, leading to resource cleanup failures. The patch changes the logic to check the GuC running state before deregistration and directly release resources if GuC is not running, preventing errors such as 'GUC ID manager unclean'.
Potential Impact
This vulnerability can cause improper cleanup of GPU exec queue resources, potentially leading to driver errors and instability in the graphics subsystem. The CVSS vector indicates high impact on confidentiality, integrity, and availability, but no known exploits are reported in the wild.
Mitigation Recommendations
A fix has been implemented in the Linux kernel to address this issue by checking the GuC running state before deregistering exec queues and releasing resources directly if GuC is not running. Users should apply the updated kernel version containing this patch once available. Patch status is not explicitly confirmed in the provided data; check the vendor or Linux kernel advisories for the official fix and update guidance.
In the Linux kernel, the following vulnerability has been resolved: drm/xe/guc: Check GuC running state before deregistering exec queue In normal… (CVE-2025-40166)
Description
A vulnerability in the Linux kernel's drm/xe/guc driver was resolved that could lead to improper cleanup of exec queue resources if the driver is forced to unbind while the exec queue is still running. This occurs because the driver may attempt to deregister an exec queue after the GuC (Graphics microcontroller) has stopped and communication is disabled, preventing proper resource cleanup and causing errors. The fix ensures resources are released directly when the GuC is not running.
CVSS v3.1
Score 7.8high
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability in the Linux kernel drm/xe/guc component involves the deregistration of exec queues without verifying the GuC running state. Normally, exec queues are deregistered only after GuC confirms completion. However, if the driver unbinds while the exec queue is active and GuC communication is disabled, the driver cannot receive responses, leading to resource cleanup failures. The patch changes the logic to check the GuC running state before deregistration and directly release resources if GuC is not running, preventing errors such as 'GUC ID manager unclean'.
Potential Impact
This vulnerability can cause improper cleanup of GPU exec queue resources, potentially leading to driver errors and instability in the graphics subsystem. The CVSS vector indicates high impact on confidentiality, integrity, and availability, but no known exploits are reported in the wild.
Mitigation Recommendations
A fix has been implemented in the Linux kernel to address this issue by checking the GuC running state before deregistering exec queues and releasing resources directly if GuC is not running. Users should apply the updated kernel version containing this patch once available. Patch status is not explicitly confirmed in the provided data; check the vendor or Linux kernel advisories for the official fix and update guidance.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-v9hw-4wx3-7mqf
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2025-40166"]
- Database Specific Severity
- HIGH
- Cvss Version
- 3.1
Threat ID: 6a6b72d59c2644c7f8479f66
Added to database: 07/30/2026, 15:50:45 UTC
Last enriched: 07/30/2026, 17:22:40 UTC
Last updated: 09/10/2026, 19:38:47 UTC
Views: 13
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.