In the Linux kernel, the following vulnerability has been resolved:
drm/xe: Don't free job in TDR
Freeing job in TDR is not safe as TDR can pass the run_job thread
resulting in UAF. It is only safe for free job to naturally be called by
the scheduler. Rather free job in TDR, add to pending list.
(cherry picked from commit ea2f6a77d0c40d97f4a4dc93fee4afe15d94926d)
Security readout for executives and security teams
Plain-English summary
A Linux graphics-driver race can free a GPU job while another kernel thread still uses it. This use-after-free could let a locally authenticated user crash the system or potentially compromise confidentiality and integrity. The supplied CVSS score is 7.8 (High).
Executive priority
Prioritize remediation on multi-user workstations, shared compute systems, and other hosts granting untrusted local access to affected GPU functionality. Treat as a high-priority kernel update, but not an internet-wide emergency: exploitation requires local access, and no active exploitation is established by the supplied evidence.
Technical view
CVE-2024-50149 is a CWE-416 use-after-free in Linux drm/xe timeout detection and recovery. TDR could pass the run_job thread and free a job prematurely. The correction leaves job freeing to the scheduler and places the job on a pending list instead.
Likely exposure
Exposure is limited to systems running an affected Linux kernel with the drm/xe driver and relevant GPU job/TDR paths reachable. The supplied version data identifies Linux 6.10 through entries involving 6.11.6 and 6.12, but its exact range is ambiguous; confirm against distribution guidance and fix-commit inclusion.
Exploitation context
The CVSS vector indicates local access, low complexity, low privileges, and no user interaction, with potentially high confidentiality, integrity, and availability impact. CISA KEV status is false, and the supplied sources provide no evidence of active exploitation or a public exploit.
Researcher notes
The central concurrency issue is unsafe job release during TDR racing beyond run_job, producing a potential dangling reference. The fix changes lifetime handling rather than merely adding a check. Precise vulnerable and fixed release boundaries cannot be established confidently from the supplied version entries alone; verify commit ancestry or distribution backports.
Mitigation direction
Install a vendor-supported kernel containing the referenced stable fix.
Consult the Linux distribution's advisory for exact affected and fixed package versions.
Prioritize shared or multi-user systems where untrusted local users can access the GPU.
Reboot into the corrected kernel after installation.
Validation and detection
Record the running kernel version on potentially exposed systems.
Confirm whether the drm/xe driver and relevant Intel GPU hardware are in use.
Verify the installed kernel includes either referenced stable fix commit.
After remediation, confirm the corrected kernel is running, not merely installed.
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.
cwe · low confidence lookup
CWE-416: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
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.
2CVSS vectors
3Timeline events
1ADP providers
3Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
2 official scores
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.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-416 · source CWE mapping
Use After Free
Use After Free represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.