Skip to content
VulniPulse
UnratedRed Hat Linux

Advisory [CVE-2026-64082] Fix register corruption from uninitialized cregs on error

This security Red Hat Linux advisory covers CVE-2026-64082.

CVE-2026-64082 Published Jul 19, 2026Updated by vendor Jul 19, 2026
Affected products & platforms
Red Hat LinuxUnclassified
Open vendor advisory

Android app · Google Play

Monitor future Red Hat Linux CVEs from your phone.

Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 32 official vendor sources and 160+ reviewed platform categories.

Matching phone alertsOptional email delivery

Summary

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. Only call cregs_to_regs() when the user copy succeeds.

A flaw was found in the Linux kernel, specifically within the RISC-V architecture's handling of process tracing and signal restoration. When functions like `compat_riscv_gpr_set()` or `compat_restore_sigcontext()` are invoked, they may process uninitialized stack data if a preceding user data copy operation fails.

This can lead to the corruption of a task's register state and potentially leak sensitive kernel stack contents, resulting in information disclosure and a denial of service. Red Hat severity: not rated.

Weakness: CWE-824. Red Hat lists Red Hat Enterprise Linux 10; Red Hat Enterprise Linux 6; Red Hat Enterprise Linux 7; Red Hat Enterprise Linux 8; Red Hat Enterprise Linux 9 as not affected.

Affected versions

No affected-version range was extracted from the source record. The vendor advisory is authoritative — check it before change work.

Official advisory · medium-confidence parse· fetched 6 days ago·verify at source

Fixed versions

No fixed release is recorded yet. That does not prove no patch exists — confirm against the vendor advisory.

Official advisory · medium-confidence parse· fetched 6 days ago·verify at source

Mitigation

The source record does not include mitigation steps. That is not a statement that no fix exists — read the vendor advisory below for the authoritative guidance.

Official advisory · medium-confidence parse· fetched 6 days ago·verify at source

Discussion(0)

No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.

Sign in to join the discussion.