linux-stable/arch
Stefan O'Rear 9abc3e6f11 riscv: process: Fix kernel gp leakage
[ Upstream commit d14fa1fcf6 ]

childregs represents the registers which are active for the new thread
in user context. For a kernel thread, childregs->gp is never used since
the kernel gp is not touched by switch_to. For a user mode helper, the
gp value can be observed in user space after execve or possibly by other
means.

[From the email thread]

The /* Kernel thread */ comment is somewhat inaccurate in that it is also used
for user_mode_helper threads, which exec a user process, e.g. /sbin/init or
when /proc/sys/kernel/core_pattern is a pipe. Such threads do not have
PF_KTHREAD set and are valid targets for ptrace etc. even before they exec.

childregs is the *user* context during syscall execution and it is observable
from userspace in at least five ways:

1. kernel_execve does not currently clear integer registers, so the starting
   register state for PID 1 and other user processes started by the kernel has
   sp = user stack, gp = kernel __global_pointer$, all other integer registers
   zeroed by the memset in the patch comment.

   This is a bug in its own right, but I'm unwilling to bet that it is the only
   way to exploit the issue addressed by this patch.

2. ptrace(PTRACE_GETREGSET): you can PTRACE_ATTACH to a user_mode_helper thread
   before it execs, but ptrace requires SIGSTOP to be delivered which can only
   happen at user/kernel boundaries.

3. /proc/*/task/*/syscall: this is perfectly happy to read pt_regs for
   user_mode_helpers before the exec completes, but gp is not one of the
   registers it returns.

4. PERF_SAMPLE_REGS_USER: LOCKDOWN_PERF normally prevents access to kernel
   addresses via PERF_SAMPLE_REGS_INTR, but due to this bug kernel addresses
   are also exposed via PERF_SAMPLE_REGS_USER which is permitted under
   LOCKDOWN_PERF. I have not attempted to write exploit code.

5. Much of the tracing infrastructure allows access to user registers. I have
   not attempted to determine which forms of tracing allow access to user
   registers without already allowing access to kernel registers.

Fixes: 7db91e57a0 ("RISC-V: Task implementation")
Cc: stable@vger.kernel.org
Signed-off-by: Stefan O'Rear <sorear@fastmail.com>
Reviewed-by: Alexandre Ghiti <alexghiti@rivosinc.com>
Link: https://lore.kernel.org/r/20240327061258.2370291-1-sorear@fastmail.com
Signed-off-by: Palmer Dabbelt <palmer@rivosinc.com>
Signed-off-by: Sasha Levin <sashal@kernel.org>
2024-05-02 16:23:36 +02:00
..
alpha
arc ARC: fix spare error 2024-01-25 14:37:38 -08:00
arm arm: dts: marvell: Fix maxium->maxim typo in brownstone dts 2024-04-13 12:58:00 +02:00
arm64 arm64: dts: rockchip: fix rk3399 hdmi ports node 2024-04-13 12:59:40 +02:00
c6x
csky
h8300
hexagon hexagon: vmlinux.lds.S: handle attributes section 2024-04-13 12:59:04 +02:00
ia64
m68k m68k: Fix invalid .section syntax 2023-09-19 12:20:04 +02:00
microblaze
mips MIPS: Clear Cause.BD in instruction_pointer_set 2024-03-26 18:21:46 -04:00
nds32
nios2
openrisc
parisc parisc: Strip upper 32 bit of sum in csum_ipv6_magic for 64-bit builds 2024-04-13 12:58:12 +02:00
powerpc powerpc: xor_vmx: Add '-mhard-float' to CFLAGS 2024-04-13 12:59:01 +02:00
riscv riscv: process: Fix kernel gp leakage 2024-05-02 16:23:36 +02:00
s390 s390/entry: align system call table on 8 bytes 2024-04-13 12:59:36 +02:00
sh sh: bios: Revive earlyprintk support 2023-11-20 11:06:51 +01:00
sparc sparc: vDSO: fix return value of __setup handler 2024-04-13 12:58:05 +02:00
um um: allow not setting extra rpaths in the linux binary 2024-03-15 10:48:18 -04:00
x86 x86/apic: Force native_apic_mem_read() to use the MOV instruction 2024-05-02 16:23:36 +02:00
xtensa xtensa: boot/lib: fix function prototypes 2023-10-10 21:53:31 +02:00
.gitignore
Kconfig