In the Linux kernel, the following vulnerability has been resolved: riscv: Fix register corruption from uninitialized cregs on error… (CVE-2026-64082)
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.
AI Analysis
Technical Summary
The vulnerability (CVE-2026-64082) affects the Linux kernel's RISC-V compatibility code. Specifically, the functions compat_riscv_gpr_set() and compat_restore_sigcontext() call cregs_to_regs() unconditionally, even when user memory copy operations (user_regset_copyin() and __copy_from_user()) fail. Because cregs is an uninitialized stack variable, failure in copying user data leads to uninitialized data being written into the target task's pt_regs structure, corrupting the register state and potentially leaking kernel stack information. The fix involves calling cregs_to_regs() only when the user copy operation succeeds, preventing register corruption and information leakage.
Potential Impact
The vulnerability can cause corruption of the register state of tasks running on RISC-V Linux kernels, potentially leading to incorrect program behavior or kernel instability. Additionally, it may leak kernel stack contents, which could expose sensitive information. There are no known exploits in the wild at this time.
Mitigation Recommendations
A fix has been implemented in the Linux kernel to address this issue by ensuring cregs_to_regs() is only called after successful user memory copy operations. Users should apply the official kernel updates that include this fix. Patch status is not explicitly confirmed in the provided data; therefore, check the vendor or Linux kernel advisories for the current remediation guidance.
In the Linux kernel, the following vulnerability has been resolved: riscv: Fix register corruption from uninitialized cregs on error… (CVE-2026-64082)
Description
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.
CVSS v3.1
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability (CVE-2026-64082) affects the Linux kernel's RISC-V compatibility code. Specifically, the functions compat_riscv_gpr_set() and compat_restore_sigcontext() call cregs_to_regs() unconditionally, even when user memory copy operations (user_regset_copyin() and __copy_from_user()) fail. Because cregs is an uninitialized stack variable, failure in copying user data leads to uninitialized data being written into the target task's pt_regs structure, corrupting the register state and potentially leaking kernel stack information. The fix involves calling cregs_to_regs() only when the user copy operation succeeds, preventing register corruption and information leakage.
Potential Impact
The vulnerability can cause corruption of the register state of tasks running on RISC-V Linux kernels, potentially leading to incorrect program behavior or kernel instability. Additionally, it may leak kernel stack contents, which could expose sensitive information. There are no known exploits in the wild at this time.
Mitigation Recommendations
A fix has been implemented in the Linux kernel to address this issue by ensuring cregs_to_regs() is only called after successful user memory copy operations. Users should apply the official kernel updates that include this fix. Patch status is not explicitly confirmed in the provided data; therefore, check the vendor or Linux kernel advisories for the current remediation guidance.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-87cj-725f-6hr5
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-64082"]
- Ecosystems
- []
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a5d27a92a4a8d598912c572
Added to database: 07/19/2026, 19:38:17 UTC
Last enriched: 07/19/2026, 19:53:28 UTC
Last updated: 07/20/2026, 19:41:22 UTC
Views: 11
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.