First published: Thu Feb 27 2025(Updated: )
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.
Credit: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Affected Software | Affected Version | How to fix |
---|---|---|
Linux Kernel | >=6.10 | |
Linux Kernel | >=6.11<6.12.16 | |
Linux Kernel | >=6.13<6.13.4 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2024-49570 is categorized as a medium severity vulnerability in the Linux kernel.
To fix CVE-2024-49570, ensure that you update to the latest version of the Linux kernel where the vulnerability has been patched.
CVE-2024-49570 affects all Linux kernel versions starting from 6.10.
CVE-2024-49570 is classified as a use-after-free (UAF) vulnerability related to the tracing infrastructure in the Linux kernel.
CVE-2024-49570 impacts the DRM (Direct Rendering Manager) tracing functionality within the Linux kernel.