CVE-2024-49876: drm/xe: fix UAF around queue destruction
In the Linux kernel, the following vulnerability has been resolved:
drm/xe: fix UAF around queue destruction
We currently do stuff like queuing the final destruction step on a
random system wq, which will outlive the driver instance. With bad
timing we can teardown the driver with one or more work workqueue still
being alive leading to various UAF splats. Add a fini step to ensure
user queues are properly torn down. At this point GuC should already be
nuked so queue itself should no longer be referenced from hw pov.
v2 (Matt B)
- Looks much safer to use a waitqueue and then just wait for the
xa_array to become empty before triggering the drain.
(cherry picked from commit 861108666cc0e999cffeab6aff17b662e68774e3)
Security readout for executives and security teams
Plain-English summary
A Linux drm/xe graphics-driver cleanup race can leave queued destruction work running after the driver has been removed. That stale work may access freed memory, potentially causing crashes or compromising confidentiality, integrity, and availability. Exploitation requires local, low-privileged access; no user interaction is required.
Executive priority
Treat as a high-priority kernel update on exposed multi-user or graphics-enabled Linux systems. It is less urgent where drm/xe is absent or local access is tightly controlled. No supplied evidence supports emergency incident response for active exploitation.
Technical view
Queue destruction was scheduled on a system workqueue that could outlive the drm/xe driver instance. During teardown, outstanding work could dereference freed objects, producing use-after-free faults. The correction adds a finalization stage that waits for the user-queue array to empty before draining destruction work.
Likely exposure
Exposure is limited to Linux systems running an affected kernel with the drm/xe driver in use. The supplied record lists 6.8, 6.10.14, 6.11.3, and 6.12 as affected, but its version data is ambiguous. Confirm distribution-specific status rather than relying solely on version strings.
Exploitation context
The CVSS 3.1 score is 7.8 with local access and low privileges required. CISA KEV status is false, and the supplied sources provide no evidence of active exploitation or a public exploit. Practical reach depends on local access and the affected driver being present and exercised.
Researcher notes
The vulnerable lifecycle crosses driver teardown and asynchronous workqueue execution. Relevant review areas include queue ownership, teardown ordering, waitqueue synchronization, and whether the queue array reaches empty before draining. The supplied record does not establish reliable affected ranges, exploitation reliability, or distribution-specific fixes.
Mitigation direction
Apply a vendor-supported kernel containing the referenced drm/xe queue-destruction fix.
Check distribution security advisories for corrected package versions and backports.
Prioritize multi-user systems where untrusted local users can access graphics resources.
Restrict unnecessary local accounts and graphics-device access while remediation is pending.
Validation and detection
Inventory kernel versions and determine whether the drm/xe driver is loaded or used.
Compare installed kernel packages with distribution advisories and referenced stable commits.
Confirm the replacement kernel is active after updating and rebooting.
Review kernel logs for use-after-free reports or drm/xe teardown faults.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2024-49876 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.