| 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-2023-52992: bpf: Skip task with pid=1 in send_signal_common() |
| |
| Description |
| =========== |
| |
| In the Linux kernel, the following vulnerability has been resolved: |
| |
| bpf: Skip task with pid=1 in send_signal_common() |
| |
| The following kernel panic can be triggered when a task with pid=1 attaches |
| a prog that attempts to send killing signal to itself, also see [1] for more |
| details: |
| |
| Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b |
| CPU: 3 PID: 1 Comm: systemd Not tainted 6.1.0-09652-g59fe41b5255f #148 |
| Call Trace: |
| <TASK> |
| __dump_stack lib/dump_stack.c:88 [inline] |
| dump_stack_lvl+0x100/0x178 lib/dump_stack.c:106 |
| panic+0x2c4/0x60f kernel/panic.c:275 |
| do_exit.cold+0x63/0xe4 kernel/exit.c:789 |
| do_group_exit+0xd4/0x2a0 kernel/exit.c:950 |
| get_signal+0x2460/0x2600 kernel/signal.c:2858 |
| arch_do_signal_or_restart+0x78/0x5d0 arch/x86/kernel/signal.c:306 |
| exit_to_user_mode_loop kernel/entry/common.c:168 [inline] |
| exit_to_user_mode_prepare+0x15f/0x250 kernel/entry/common.c:203 |
| __syscall_exit_to_user_mode_work kernel/entry/common.c:285 [inline] |
| syscall_exit_to_user_mode+0x1d/0x50 kernel/entry/common.c:296 |
| do_syscall_64+0x44/0xb0 arch/x86/entry/common.c:86 |
| entry_SYSCALL_64_after_hwframe+0x63/0xcd |
| |
| So skip task with pid=1 in bpf_send_signal_common() to avoid the panic. |
| |
| [1] https://lore.kernel.org/bpf/20221222043507.33037-1-sunhao.th@gmail.com |
| |
| The Linux kernel CVE team has assigned CVE-2023-52992 to this issue. |
| |
| |
| Affected and fixed versions |
| =========================== |
| |
| Fixed in 5.4.231 with commit 4923160393b06a34759a11b17930d71e06f396f2 |
| Fixed in 5.10.167 with commit a1c0263f1eb4deee132e11e52ee6982435460d81 |
| Fixed in 5.15.92 with commit 0dfef503133565fa0bcf3268d8eeb5b181191a65 |
| Fixed in 6.1.10 with commit 1283a01b6e19d05f7ed49584ea653947245cd41e |
| Fixed in 6.2 with commit a3d81bc1eaef48e34dd0b9b48eefed9e02a06451 |
| |
| 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-2023-52992 |
| 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/bpf_trace.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/4923160393b06a34759a11b17930d71e06f396f2 |
| https://git.kernel.org/stable/c/a1c0263f1eb4deee132e11e52ee6982435460d81 |
| https://git.kernel.org/stable/c/0dfef503133565fa0bcf3268d8eeb5b181191a65 |
| https://git.kernel.org/stable/c/1283a01b6e19d05f7ed49584ea653947245cd41e |
| https://git.kernel.org/stable/c/a3d81bc1eaef48e34dd0b9b48eefed9e02a06451 |
