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 TPprintk UAF
The commit afd2627f727b ("tracing: Check "%s" dereference via the field and not the TPprintk format") exposes potential UAFs in the xebomove trace event.
Fix those by avoiding dereferencing the xememtypetoname[] array at TPprintk time.
Since some code refactoring has taken place, explicit backporting may be needed for kernels older than 6.10.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Linux kernelto a version that resolves this vulnerability.Patch afd2627f727b
Event History
Frequently Asked Questions
What is the severity of CVE-2024-49570?
CVE-2024-49570 is categorized as a medium severity vulnerability in the Linux kernel.
How do I fix CVE-2024-49570?
To fix CVE-2024-49570, ensure that you update to the latest version of the Linux kernel where the vulnerability has been patched.
Which versions of the Linux kernel are affected by CVE-2024-49570?
CVE-2024-49570 affects all Linux kernel versions starting from 6.10.
What type of vulnerability is CVE-2024-49570?
CVE-2024-49570 is classified as a use-after-free (UAF) vulnerability related to the tracing infrastructure in the Linux kernel.
What components are impacted by CVE-2024-49570?
CVE-2024-49570 impacts the DRM (Direct Rendering Manager) tracing functionality within the Linux kernel.