CVE-2024-49570
Published: 27 February 2025
Summary
CVE-2024-49570 is a high-severity Use After Free (CWE-416) vulnerability in Linux Linux Kernel. Its CVSS base score is 7.8 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked at the 3.0th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified are NIST 800-53 SI-2 (Flaw Remediation) and RA-5 (Vulnerability Monitoring and Scanning).
Deeper analysis
CVE-2024-49570 is a Use After Free (UAF) vulnerability in the Linux kernel's drm/xe/tracing subsystem, specifically affecting the xe_bo_move trace event. The issue stems from a prior commit that exposed potential UAFs by dereferencing the xe_mem_type_to_name[] array during TP_printk processing. It impacts Linux kernels, with explicit backporting required for versions older than 6.10 due to code refactoring.
A local attacker with low privileges can exploit this vulnerability with low complexity and no user interaction, as indicated by its CVSS v3.1 base score of 7.8 (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H). Successful exploitation could allow the attacker to achieve high impacts on confidentiality, integrity, and availability, potentially leading to arbitrary code execution or system crashes within the kernel context.
The provided patch references detail the fix by avoiding dereference of the xe_mem_type_to_name[] array at TP_printk time. Kernel stable trees have applied commits such as 07089083a526, 62cd174616ae, and c9402da34611 to resolve the issue, emphasizing the need for manual backports to older kernels.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-5229
Vulnerability details
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…
more
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.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise TechniquesAI
Why these techniques?
Local kernel UAF enables direct exploitation for privilege escalation to achieve arbitrary code execution.
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Directly remediates the UAF vulnerability by requiring timely application of kernel patches that prevent dereferencing the xe_mem_type_to_name array at TP_printk time.
Mitigates exploitation of the UAF in the drm/xe tracing subsystem by implementing memory protections against unauthorized code execution from memory access violations.
Identifies the kernel UAF vulnerability through vulnerability scanning, enabling prompt remediation before local low-privilege exploitation.