| From bippy-5f407fcff5a0 Mon Sep 17 00:00:00 2001 |
| From: Greg Kroah-Hartman <gregkh@linuxfoundation.org> |
| To: <linux-cve-announce@vger.kernel.org> |
| Reply-to: <cve@kernel.org>, <linux-kernel@vger.kernel.org> |
| Subject: CVE-2024-49570: drm/xe/tracing: Fix a potential TP_printk UAF |
| |
| 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. |
| |
| The Linux kernel CVE team has assigned CVE-2024-49570 to this issue. |
| |
| |
| Affected and fixed versions |
| =========================== |
| |
| Issue introduced in 6.11 with commit e46d3f813abd2383881c66d21ba04cee9fbdf3a9 and fixed in 6.12.16 with commit 62cd174616ae3bf8a6cf468718f1ae74e5a07727 |
| Issue introduced in 6.11 with commit e46d3f813abd2383881c66d21ba04cee9fbdf3a9 and fixed in 6.13.4 with commit c9402da34611e1039ecccba3c1481c4866f7ca64 |
| Issue introduced in 6.11 with commit e46d3f813abd2383881c66d21ba04cee9fbdf3a9 and fixed in 6.14 with commit 07089083a526ea19daa72a1edf9d6e209615b77c |
| |
| Please see https://www.kernel.org for a full list of currently supported |
| kernel versions by the kernel community. |
| |
| Unaffected versions might change over time as fixes are backported to |
| older supported kernel versions. The official CVE entry at |
| https://cve.org/CVERecord/?id=CVE-2024-49570 |
| will be updated if fixes are backported, please check that for the most |
| up to date information about this issue. |
| |
| |
| Affected files |
| ============== |
| |
| The file(s) affected by this issue are: |
| drivers/gpu/drm/xe/xe_trace_bo.h |
| |
| |
| Mitigation |
| ========== |
| |
| The Linux kernel CVE team recommends that you update to the latest |
| stable kernel version for this, and many other bugfixes. Individual |
| changes are never tested alone, but rather are part of a larger kernel |
| release. Cherry-picking individual commits is not recommended or |
| supported by the Linux kernel community at all. If however, updating to |
| the latest release is impossible, the individual changes to resolve this |
| issue can be found at these commits: |
| https://git.kernel.org/stable/c/62cd174616ae3bf8a6cf468718f1ae74e5a07727 |
| https://git.kernel.org/stable/c/c9402da34611e1039ecccba3c1481c4866f7ca64 |
| https://git.kernel.org/stable/c/07089083a526ea19daa72a1edf9d6e209615b77c |
