Vulnerability Description
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.
CVSS Score
HIGH
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux Kernel | >= 6.11, < 6.12.16 |
Related Weaknesses (CWE)
References
- https://git.kernel.org/stable/c/07089083a526ea19daa72a1edf9d6e209615b77cPatch
- https://git.kernel.org/stable/c/62cd174616ae3bf8a6cf468718f1ae74e5a07727Patch
- https://git.kernel.org/stable/c/c9402da34611e1039ecccba3c1481c4866f7ca64Patch
FAQ
What is CVE-2024-49570?
CVE-2024-49570 is a vulnerability with a CVSS score of 7.8 (HIGH). 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 ...
How severe is CVE-2024-49570?
CVE-2024-49570 has been rated HIGH with a CVSS base score of 7.8/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2024-49570?
Check the references section above for vendor advisories and patch information. Affected products include: Linux Linux Kernel.