CVE-2026-64082 json
riscv: Fix register corruption from uninitialized cregs on error
published 2026-07-19 3 mo ago modified 2026-09-03 2 mo ago also EUVD-2026-45655
- cvss
- 7.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.1%
- EPSS 0.1% chance of exploitation in 30 days, percentile 2%
- public exploits
- 0
- none known
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. 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.
Patch / fix
- Linux Linux 6.1.187, 6.6.156, 6.12.108, 6.18.49, 7.0.11, 7.1
- linux Debian 12 6.1.187-1
- linux Debian 13 6.12.111-1
- linux Debian 14 7.0.12-1
- linux-6.12 Debian 12 6.12.111-1~deb12u1
debian advisories DEBIAN-CVE-2026-64082
- linux Ubuntu 26.04 LTS 7.0.0-28.28
- linux-aws Ubuntu 26.04 LTS 7.0.0-1009.9
- linux-gcp Ubuntu 26.04 LTS 7.0.0-1008.8
- linux-gke Ubuntu 26.04 LTS 7.0.0-1003.4
- linux-ibm Ubuntu 26.04 LTS 7.0.0-1010.10
- linux-azure Ubuntu 26.04 LTS 7.0.0-1010.10
- linux-raspi Ubuntu 26.04 LTS 7.0.0-1015.15
- linux-riscv Ubuntu 26.04 LTS 7.0.0-28.28.1
ubuntu advisories UBUNTU-CVE-2026-64082
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- git.kernel.org/stable/c/f2d88b0d7aebfa4643fc58bbae57210c6daff9c6 commit
- git.kernel.org/stable/c/66dedb6028c3df6c6a3372dd935b823917e150d5 commit
- git.kernel.org/stable/c/2a7d1daf2674fe7d5b1cc99a4e3b5f0f72d5958f commit
- git.kernel.org/stable/c/0599aa23734c48de9bce36d043a9ec90c23945a1 commit
- git.kernel.org/stable/c/9e020156833f1ad0d425a1e3d85b65639f1c1c50 commit
- git.kernel.org/stable/c/6ebcbb53fc9bc30843054ed99fd60b8e542628f4 commit
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-64082 updated
kernel: riscv: Fix register corruption from uninitialized cregs on error
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more Red Hat Enterprise Linux 10 kernelnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.13% chance of exploitation in the next 30 days, higher than 2% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
Affected products
- Linux Linux
Classification
- Weakness
-
- CWE-908 Use of Uninitialized Resource
- Technology feeds
References
-
git.kernel.org
/stable/c/f2d88b0d7aebfa4643fc58bbae57210c6daff9c6
patch
-
git.kernel.org
/stable/c/66dedb6028c3df6c6a3372dd935b823917e150d5
patch
-
git.kernel.org
/stable/c/2a7d1daf2674fe7d5b1cc99a4e3b5f0f72d5958f
patch
-
git.kernel.org
/stable/c/0599aa23734c48de9bce36d043a9ec90c23945a1
patch
-
git.kernel.org
/stable/c/9e020156833f1ad0d425a1e3d85b65639f1c1c50
patch
-
git.kernel.org
/stable/c/6ebcbb53fc9bc30843054ed99fd60b8e542628f4
patch
Sources
- CVE List CVE-2026-64082
- NVD CVE-2026-64082
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.