CVE-2024-49570

7.8 HIGH

📋 TL;DR

This CVE describes a use-after-free vulnerability in the Linux kernel's DRM/Xe graphics subsystem trace event handling. An attacker with local access could potentially exploit this to cause kernel memory corruption, leading to system crashes or privilege escalation. Systems running affected Linux kernel versions with Xe graphics driver tracing enabled are vulnerable.

💻 Affected Systems

Products:
  • Linux kernel with Xe graphics driver
Versions: Linux kernel versions before 6.10 with specific commits backported; explicit backporting may be needed for older kernels.
Operating Systems: Linux distributions using affected kernel versions
Default Config Vulnerable: ⚠️ Yes
Notes: Requires Xe graphics driver tracing to be enabled/active. The vulnerability is in the trace event handling code.

📦 What is this software?

Linux Kernel by Linux

The Linux Kernel is the core component of the Linux operating system, serving as the critical interface between computer hardware and software processes. As the heart of millions of servers, cloud infrastructure, embedded systems, Android devices, and IoT deployments worldwide, the Linux Kernel mana...

Learn more about Linux Kernel →

Linux Kernel by Linux

The Linux Kernel is the core component of the Linux operating system, serving as the critical interface between computer hardware and software processes. As the heart of millions of servers, cloud infrastructure, embedded systems, Android devices, and IoT deployments worldwide, the Linux Kernel mana...

Learn more about Linux Kernel →

⚠️ Risk & Real-World Impact

🔴

Worst Case

Local privilege escalation to root, kernel panic causing system instability, or potential arbitrary code execution in kernel context.

🟠

Likely Case

Kernel crash or denial of service when specific trace events are triggered, potentially requiring system reboot.

🟢

If Mitigated

Limited impact if tracing is disabled or the system has proper kernel hardening protections like KASLR and SMEP/SMAP.

🌐 Internet-Facing: LOW - This is a local kernel vulnerability requiring access to the system.
🏢 Internal Only: MEDIUM - Local users or compromised applications could exploit this for privilege escalation or DoS attacks.

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: UNKNOWN
Unauthenticated Exploit: ✅ No
Complexity: MEDIUM

Requires local access and ability to trigger specific trace events. The UAF occurs during TP_printk formatting in trace events.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Linux kernel 6.10 and later; specific stable commits: 07089083a526ea19daa72a1edf9d6e209615b77c, 62cd174616ae3bf8a6cf468718f1ae74e5a07727, c9402da34611e1039ecccba3c1481c4866f7ca64

Vendor Advisory: https://git.kernel.org/stable/c/07089083a526ea19daa72a1edf9d6e209615b77c

Restart Required: Yes

Instructions:

1. Update Linux kernel to version 6.10 or later. 2. For older kernels, apply the specific stable commits. 3. Reboot the system to load the new kernel.

🔧 Temporary Workarounds

Disable Xe driver tracing

Linux

Disable tracing for the Xe graphics driver to prevent the vulnerable code path from being triggered.

echo 0 > /sys/kernel/debug/tracing/events/drm/xe_bo_move/enable
echo 0 > /sys/kernel/debug/tracing/events/drm/enable

🧯 If You Can't Patch

  • Disable all kernel tracing functionality system-wide
  • Restrict local user access and implement strict privilege separation

🔍 How to Verify

Check if Vulnerable:

Check kernel version and if Xe driver tracing is active: uname -r and check /sys/kernel/debug/tracing/events/drm/xe_bo_move/enable

Check Version:

uname -r

Verify Fix Applied:

Verify kernel version is 6.10 or later, or check that the specific commit hashes are present in kernel source.

📡 Detection & Monitoring

Log Indicators:

  • Kernel oops messages, system crashes, trace event errors in kernel logs

Network Indicators:

  • None - this is a local vulnerability

SIEM Query:

Search for kernel panic messages or trace event failures in system logs

🔗 References

📤 Share & Export