[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025032705-CVE-2023-52978-6a05@gregkh>
Date: Thu, 27 Mar 2025 17:43:25 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: CVE-2023-52978: riscv: kprobe: Fixup kernel panic when probing an illegal position
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
riscv: kprobe: Fixup kernel panic when probing an illegal position
The kernel would panic when probed for an illegal position. eg:
(CONFIG_RISCV_ISA_C=n)
echo 'p:hello kernel_clone+0x16 a0=%a0' >> kprobe_events
echo 1 > events/kprobes/hello/enable
cat trace
Kernel panic - not syncing: stack-protector: Kernel stack
is corrupted in: __do_sys_newfstatat+0xb8/0xb8
CPU: 0 PID: 111 Comm: sh Not tainted
6.2.0-rc1-00027-g2d398fe49a4d #490
Hardware name: riscv-virtio,qemu (DT)
Call Trace:
[<ffffffff80007268>] dump_backtrace+0x38/0x48
[<ffffffff80c5e83c>] show_stack+0x50/0x68
[<ffffffff80c6da28>] dump_stack_lvl+0x60/0x84
[<ffffffff80c6da6c>] dump_stack+0x20/0x30
[<ffffffff80c5ecf4>] panic+0x160/0x374
[<ffffffff80c6db94>] generic_handle_arch_irq+0x0/0xa8
[<ffffffff802deeb0>] sys_newstat+0x0/0x30
[<ffffffff800158c0>] sys_clone+0x20/0x30
[<ffffffff800039e8>] ret_from_syscall+0x0/0x4
---[ end Kernel panic - not syncing: stack-protector:
Kernel stack is corrupted in: __do_sys_newfstatat+0xb8/0xb8 ]---
That is because the kprobe's ebreak instruction broke the kernel's
original code. The user should guarantee the correction of the probe
position, but it couldn't make the kernel panic.
This patch adds arch_check_kprobe in arch_prepare_kprobe to prevent an
illegal position (Such as the middle of an instruction).
The Linux kernel CVE team has assigned CVE-2023-52978 to this issue.
Affected and fixed versions
===========================
Issue introduced in 5.12 with commit c22b0bcb1dd024cb9caad9230e3a387d8b061df5 and fixed in 5.15.93 with commit 04a73558209554da17f46490ec4faaaf1b2bab68
Issue introduced in 5.12 with commit c22b0bcb1dd024cb9caad9230e3a387d8b061df5 and fixed in 6.1.11 with commit 12316538b1d193064109ce1a28fc9bacd43950de
Issue introduced in 5.12 with commit c22b0bcb1dd024cb9caad9230e3a387d8b061df5 and fixed in 6.2 with commit 87f48c7ccc73afc78630530d9af51f458f58cab8
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-52978
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:
arch/riscv/kernel/probes/kprobes.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/04a73558209554da17f46490ec4faaaf1b2bab68
https://git.kernel.org/stable/c/12316538b1d193064109ce1a28fc9bacd43950de
https://git.kernel.org/stable/c/87f48c7ccc73afc78630530d9af51f458f58cab8
Powered by blists - more mailing lists