Linux: Use of Uninitialized Resource
CVE-2026-64082 is a high-severity use of uninitialized resource vulnerability in Linux, with a CVSS 3.1 base score of 7.8 out of 10. It can be exploited with local access to the system by an attacker with a low-privileged account, without any action from a user. The record lists versions f2d88b0d7aebfa4643fc58bbae57210c6daff9c6, 66dedb6028c3df6c6a3372dd935b823917e150d5, 2a7d1daf2674fe7d5b1cc99a4e3b5f0f72d5958f as the first without the flaw, so updating Linux to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.13% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update Linux to f2d88b0d7aebfa4643fc58bbae57210c6daff9c6 or 66dedb6028c3df6c6a3372dd935b823917e150d5 or 2a7d1daf2674fe7d5b1cc99a4e3b5f0f72d5958f or 0599aa23734c48de9bce36d043a9ec90c23945a1, whichever matches your release line, or a later version.
- Update Linux Kernel to 7.0.11 or a later version.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Linux | Linux | 7383ee05314be58f8f9f018ee0ac53bef3808aea up to, but not including, f2d88b0d7aebfa4643fc58bbae57210c6daff9c6; 7383ee05314be58f8f9f018ee0ac53bef3808aea up to, but not including, 66dedb6028c3df6c6a3372dd935b823917e150d5; 7383ee05314be58f8f9f018ee0ac53bef3808aea up to, but not including, 2a7d1daf2674fe7d5b1cc99a4e3b5f0f72d5958f; 7383ee05314be58f8f9f018ee0ac53bef3808aea up to, but not including, 0599aa23734c48de9bce36d043a9ec90c23945a1; 7383ee05314be58f8f9f018ee0ac53bef3808aea up to, but not including, 9e020156833f1ad0d425a1e3d85b65639f1c1c50; 7383ee05314be58f8f9f018ee0ac53bef3808aea up to, but not including, 6ebcbb53fc9bc30843054ed99fd60b8e542628f4; 5.19 | f2d88b0d7aebfa4643fc58bbae57210c6daff9c6, 66dedb6028c3df6c6a3372dd935b823917e150d5, 2a7d1daf2674fe7d5b1cc99a4e3b5f0f72d5958f, 0599aa23734c48de9bce36d043a9ec90c23945a1, 9e020156833f1ad0d425a1e3d85b65639f1c1c50, 6ebcbb53fc9bc30843054ed99fd60b8e542628f4 |
| Linux | Linux Kernel | 5.19 up to, but not including, 7.0.11; 7.1 | 7.0.11 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- LocalThe attacker needs local access or must trick a user into running something.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- LowA basic user account is enough.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. Scored by CNA.
Official 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.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Use of Uninitialized Resource
The product uses or accesses a resource that has not been initialized.
How developers prevent this class of flaw
- Explicitly initialize the resource before use. If this is performed through an API function or standard procedure, follow all required steps.
- Pay close attention to complex conditionals that affect initialization, since some branches might not perform the initialization.
- Avoid race conditions (CWE-362) during initialization routines.
More Use of Uninitialized Resource vulnerabilities (CWE-908)
Timeline
- CVE record published.
- Record last changed materially (score, affected products, status or references).
References
Patches and release notes
- git.kernel.org/stable/c/0599aa23734c48de9bce36d043a9ec90c23945a1
- git.kernel.org/stable/c/2a7d1daf2674fe7d5b1cc99a4e3b5f0f72d5958f
- git.kernel.org/stable/c/66dedb6028c3df6c6a3372dd935b823917e150d5
- git.kernel.org/stable/c/6ebcbb53fc9bc30843054ed99fd60b8e542628f4
- git.kernel.org/stable/c/9e020156833f1ad0d425a1e3d85b65639f1c1c50
- git.kernel.org/stable/c/f2d88b0d7aebfa4643fc58bbae57210c6daff9c6
Recent Use of Uninitialized Resource vulnerabilities
- 7.8 High severity
- 9.8 Critical severity
- 8.2 High severity
- 9.1 Critical severity
- 8.8 High severity
- 9.8 Critical severity
Spotted an error? Tell us.