CVE-2024-49570

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 Metrics

• v3.1•HIGH•Score: 7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

EPSS Trends

Current EPSS score: 0.01%• Percentile: 3%

Techniques & Countermeasures

• CWE-416•Use After Free

  The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer.

Affected Systems

• linux•linux

  ≥ e46d3f813abd2383881c66d21ba04cee9fbdf3a9, < 62cd174616ae3bf8a6cf468718f1ae74e5a07727 | ≥ e46d3f813abd2383881c66d21ba04cee9fbdf3a9, < c9402da34611e1039ecccba3c1481c4866f7ca64 | ≥ e46d3f813abd2383881c66d21ba04cee9fbdf3a9, < 07089083a526ea19daa72a1edf9d6e209615b77c | 6.11

• linux•linux_kernel

  ≥ 6.11, < 6.12.16 | ≥ 6.13, < 6.13.4

References (3)

• https://git.kernel.org/stable/c/62cd174616ae3bf8a6cf468718f1ae74e5a07727
• https://git.kernel.org/stable/c/c9402da34611e1039ecccba3c1481c4866f7ca64
• https://git.kernel.org/stable/c/07089083a526ea19daa72a1edf9d6e209615b77c