riscv: Fix register corruption from uninitialized cregs on error
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 7383ee05314be58f8f9f018ee0ac53bef3808aea · < 6ebcbb53fc9bc30843054ed99fd60b8e542628f4| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
riscv: Fix register corruption from uninitialized cregs on error
compat_riscv_gpr_set() calls cregs_to_regs() unconditionally, even when user_regset_copyin() fails. Since cregs is an uninitialized stack variable, a copyin failure causes uninitialized stack data to be written into the target task's pt_regs, corrupting its register state and potentially leaking kernel stack contents.
compat_restore_sigcontext() has the same issue: it calls cregs_to_regs() even when __copy_from_user() fails, leading to the same corruption of the signal-returning task's register state on error.
Only call cregs_to_regs() when the user copy succeeds.
From the CVE record · Linux
The Linux kernel’s RISC-V compatibility code can copy uninitialized stack data into task registers when a copy from user memory fails. This can corrupt register state and potentially leak kernel stack contents. The described trigger is a local user-memory copy failure; authentication requirements and user interaction are not specified.
Engineers running Linux kernels with the affected RISC-V compatibility code should check their kernel versions; no affected versions are specified.