CVE-2024-44978: drm/xe: Free job before xe_exec_queue_put
In the Linux kernel, the following vulnerability has been resolved:
drm/xe: Free job before xe_exec_queue_put
Free job depends on job->vm being valid, the last xe_exec_queue_put can
destroy the VM. Prevent UAF by freeing job before xe_exec_queue_put.
(cherry picked from commit 32a42c93b74c8ca6d0915ea3eba21bceff53042f)
Security readout for executives and security teams
Plain-English summary
A flaw in the Linux Intel Xe graphics driver can leave a job referring to an already-destroyed virtual-memory object. A local, low-privileged attacker may be able to trigger memory corruption, potentially compromising confidentiality, integrity, and system availability. The supplied score is CVSS 7.8.
Executive priority
Treat as a high-priority kernel update for workstations, shared compute, and other systems using Intel Xe graphics with untrusted local access. It warrants expedited remediation, but the supplied evidence does not support an internet-wide exploitation emergency or direct remote attack scenario.
Technical view
This is a use-after-free caused by cleanup ordering in drm/xe. The final xe_exec_queue_put can destroy the VM while job cleanup still depends on job->vm. The Linux fix frees the job before releasing the execution queue, preserving the VM until job cleanup completes.
Likely exposure
Exposure requires a vulnerable Linux kernel containing the affected drm/xe code and access to the relevant local GPU execution path. The supplied version data names 6.8, 6.10.7, and 6.11 markers but does not clearly preserve exact affected ranges; confirm mappings with the kernel or distribution vendor.
Exploitation context
The CVSS vector describes local access, low complexity, low privileges, and no user interaction. The source bundle marks this CVE as absent from KEV and provides no evidence of active exploitation, public weaponization, or remote exploitation.
Researcher notes
The security boundary is local according to CVSS. Investigation should focus on whether drm/xe execution queues are reachable by untrusted principals and whether downstream kernels backported either referenced fix. No CWE, proof of concept, exploitation telemetry, or reliable detection signature is supplied. Avoid determining exposure from version strings alone because distributor backports may differ.
Mitigation direction
Update to a vendor-supported kernel incorporating the applicable referenced Linux stable fix.
Prioritize systems actively using drm/xe and permitting access by untrusted local users or workloads.
If updating is delayed, consult the Linux distribution vendor; the supplied sources identify no configuration workaround.
Reboot into the remediated kernel after installation, following vendor operational guidance.
Validation and detection
Inventory running kernel builds and determine whether the drm/xe driver is present and active.
Check vendor advisories or package changelogs for backport confirmation covering CVE-2024-44978.
Verify source or provenance contains the applicable stable cleanup-ordering fix.
After reboot, confirm systems are running the intended remediated kernel build.
Review kernel and GPU fault telemetry, noting that the sources provide no compromise indicators.
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-44978 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.