https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sun, 04 Oct 2026 08:45:49 +0000 https://vulnerability.circl.lu/vuln/cve-2026-64082 <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>riscv: Fix register corruption from uninitialized cregs on error</p> <p>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&#39;s pt_regs, corrupting its register state and potentially leaking kernel stack contents.</p> <p>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&#39;s register state on error.</p> <p>Only call cregs_to_regs() when the user copy succeeds.</p> <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>riscv: Fix register corruption from uninitialized cregs on error</p> <p>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&#39;s pt_regs, corrupting its register state and potentially leaking kernel stack contents.</p> <p>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&#39;s register state on error.</p> <p>Only call cregs_to_regs() when the user copy succeeds.</p> https://vulnerability.circl.lu/vuln/cve-2026-64082