| 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-50132: tracing/probes: Fix MAX_TRACE_ARGS limit handling |
| |
| Description |
| =========== |
| |
| In the Linux kernel, the following vulnerability has been resolved: |
| |
| tracing/probes: Fix MAX_TRACE_ARGS limit handling |
| |
| When creating a trace_probe we would set nr_args prior to truncating the |
| arguments to MAX_TRACE_ARGS. However, we would only initialize arguments |
| up to the limit. |
| |
| This caused invalid memory access when attempting to set up probes with |
| more than 128 fetchargs. |
| |
| BUG: kernel NULL pointer dereference, address: 0000000000000020 |
| #PF: supervisor read access in kernel mode |
| #PF: error_code(0x0000) - not-present page |
| PGD 0 P4D 0 |
| Oops: Oops: 0000 [#1] PREEMPT SMP PTI |
| CPU: 0 UID: 0 PID: 1769 Comm: cat Not tainted 6.11.0-rc7+ #8 |
| Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.3-1.fc39 04/01/2014 |
| RIP: 0010:__set_print_fmt+0x134/0x330 |
| |
| Resolve the issue by applying the MAX_TRACE_ARGS limit earlier. Return |
| an error when there are too many arguments instead of silently |
| truncating. |
| |
| The Linux kernel CVE team has assigned CVE-2024-50132 to this issue. |
| |
| |
| Affected and fixed versions |
| =========================== |
| |
| Issue introduced in 6.9 with commit 035ba76014c096316fa809a46ce0a1b9af1cde0d and fixed in 6.11.6 with commit 08ccd1a57c4d3882e9a877eb2dcc66e50a3b0279 |
| Issue introduced in 6.9 with commit 035ba76014c096316fa809a46ce0a1b9af1cde0d and fixed in 6.12 with commit 73f35080477e893aa6f4c8d388352b871b288fbc |
| |
| 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-50132 |
| 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: |
| kernel/trace/trace_eprobe.c |
| kernel/trace/trace_fprobe.c |
| kernel/trace/trace_kprobe.c |
| kernel/trace/trace_uprobe.c |
| |
| |
| 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/6bc24db74fe4788cc7c2f30a113fc6aafba225a3 |
| https://git.kernel.org/stable/c/08ccd1a57c4d3882e9a877eb2dcc66e50a3b0279 |
| https://git.kernel.org/stable/c/73f35080477e893aa6f4c8d388352b871b288fbc |
