LiveActive security incident?Get immediate response
CVE Record

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.

HighCVSS 7.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

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.
  • Avoid assuming kernel version alone proves safety; confirm vendor patch status.
  • For kernels older than 6.10, verify whether explicit backporting was applied.

Validation and detection

  • Inventory Linux hosts and record kernel package versions.
  • Confirm whether the host uses affected Xe DRM driver paths.
  • Map installed kernels to vendor advisories for CVE-2024-49570.
  • Verify the referenced stable commits or equivalent backports are present.
  • Reboot into the fixed kernel after patch installation.
Prepared
Confidence
medium
Sources
5

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.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2024-49570 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

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.

ScoreVersionSeverityVectorExploitImpactSource
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9CISA-ADP

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2024-49570Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
cvssV3_1other:ssvc
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxe46d3f813abd2383881c66d21ba04cee9fbdf3a9, e46d3f813abd2383881c66d21ba04cee9fbdf3a9, e46d3f813abd2383881c66d21ba04cee9fbdf3a9unaffected
LinuxLinux6.11, 0, 6.12.16, 6.13.4, 6.14affected
Weakness

CWE details

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.