CVE-2024-49570: drm/xe/tracing: Fix a potential TP_printk UAF
In the Linux kernel, the following vulnerability has been resolved:
drm/xe/tracing: Fix a potential TP_printk UAF
The commit
afd2627f727b ("tracing: Check "%s" dereference via the field and not the TP_printk format")
exposes potential UAFs in the xe_bo_move trace event.
Fix those by avoiding dereferencing the
xe_mem_type_to_name[] array at TP_printk time.
Since some code refactoring has taken place, explicit backporting may
be needed for kernels older than 6.10.
Security readout for executives and security teams
Plain-English summary
CVE-2024-49570 is a high-severity Linux kernel use-after-free issue in the Intel Xe DRM tracing code. A local user with some access could potentially trigger memory corruption with serious confidentiality, integrity, and availability impact. The sources do not show active exploitation or a remote attack path.
Executive priority
Treat this as a high-priority kernel patching item, not an emergency internet-facing incident. Focus on local privilege boundaries, shared systems, and endpoint fleets with Intel Xe graphics exposure. There is no cited evidence of active exploitation.
Technical view
The flaw is CWE-416 in drm/xe tracing, specifically xe_bo_move trace event printing. A tracing change exposed unsafe dereferencing at TP_printk time; the kernel fix avoids dereferencing xe_mem_type_to_name[] during TP_printk. Older kernels before 6.10 may require explicit backporting because of refactoring.
Likely exposure
Exposure is most likely on Linux systems running affected kernel builds with the Xe DRM driver path present, especially systems using newer Intel graphics. The CVSS vector is local, low complexity, low privilege, no user interaction. The provided affected-version data is not precise enough to name every vulnerable distribution package.
Exploitation context
The source bundle marks KEV as false and provides no evidence of exploitation in the wild. The vulnerability requires local privileges, so risk is higher on multi-user workstations, shared compute, developer machines, and systems where untrusted users or workloads can run locally.
Researcher notes
Key uncertainty is affected-version interpretation across distributions. The CVE states Linux kernel resolution and references three stable commits, but distro kernels may carry equivalent backports. Validate using vendor advisories and patch provenance rather than upstream version strings alone.
Mitigation direction
Update to a kernel containing the referenced stable fixes.
Check Linux distribution advisories for backported fixes to older supported kernels.
Prioritize multi-user systems and hosts using Intel Xe graphics paths.
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.
1CVSS vectors
3Timeline events
1ADP providers
4Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
1 official score
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.