Linux: Use of Uninitialized Resource
CVE-2026-31626 is a high-severity use of uninitialized resource vulnerability in Linux, with a CVSS 3.1 base score of 7.1 out of 10. It can be exploited from the same local network by an unauthenticated attacker, without any action from a user. The record lists versions 6792624d933146e2757b07092e93ad915cb58930, 51532c7c1d357145f4ac561648499f7a6847f739, 9e911eead187240193516edf55a0e1ab3425aa5b 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.29% 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 6792624d933146e2757b07092e93ad915cb58930 or 51532c7c1d357145f4ac561648499f7a6847f739 or 9e911eead187240193516edf55a0e1ab3425aa5b or c65ee4d3be5df395e48afbcd0946dd5fce4338a9, whichever matches your release line, or a later version.
- Update Linux Kernel to 6.6.136 or 6.12.83 or 6.18.24 or 6.19.14, whichever matches your release line, or a later version.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Linux | Linux | 554c0a3abf216c991c5ebddcdb2c08689ecd290b up to, but not including, 6792624d933146e2757b07092e93ad915cb58930; 554c0a3abf216c991c5ebddcdb2c08689ecd290b up to, but not including, 51532c7c1d357145f4ac561648499f7a6847f739; 554c0a3abf216c991c5ebddcdb2c08689ecd290b up to, but not including, 9e911eead187240193516edf55a0e1ab3425aa5b; 554c0a3abf216c991c5ebddcdb2c08689ecd290b up to, but not including, c65ee4d3be5df395e48afbcd0946dd5fce4338a9; 554c0a3abf216c991c5ebddcdb2c08689ecd290b up to, but not including, d5b8f5f8d6fc09a8af5ed139c688660f578ed732; 554c0a3abf216c991c5ebddcdb2c08689ecd290b up to, but not including, b487a7754d874230299d5a9c2710ec4df8b2ed8a; 554c0a3abf216c991c5ebddcdb2c08689ecd290b up to, but not including, c2026c6b603ebec52f55015496703fe79077accf; 554c0a3abf216c991c5ebddcdb2c08689ecd290b up to, but not including, ef74ce5f0bc0e53ce702d8a794f3957884a26efc; and 2 more ranges | 6792624d933146e2757b07092e93ad915cb58930, 51532c7c1d357145f4ac561648499f7a6847f739, 9e911eead187240193516edf55a0e1ab3425aa5b, c65ee4d3be5df395e48afbcd0946dd5fce4338a9, d5b8f5f8d6fc09a8af5ed139c688660f578ed732, b487a7754d874230299d5a9c2710ec4df8b2ed8a |
| Linux | Linux Kernel | 4.12 up to, but not including, 6.6.136; 6.7 up to, but not including, 6.12.83; 6.13 up to, but not including, 6.18.24; 6.19 up to, but not including, 6.19.14; 7.0 up to, but not including, 7.0.1 | 6.6.136, 6.12.83, 6.18.24, 6.19.14, 7.0.1 |
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
- AdjacentThe attacker must be on the same local network segment.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- NoneNo data is disclosed.
- Integrity
- LowLimited modification of data is possible.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H. Scored by CNA.
Official description
In the Linux kernel, the following vulnerability has been resolved: staging: rtl8723bs: initialize le_tmp64 in rtw_BIP_verify() Initialize le_tmp64 to zero in rtw_BIP_verify() to prevent using uninitialized data. Smatch warns that only 6 bytes are copied to this 8-byte (u64) variable, leaving the last two bytes uninitialized: drivers/staging/rtl8723bs/core/rtw_security.c:1308 rtw_BIP_verify() warn: not copying enough bytes for '&le_tmp64' (8 vs 6 bytes) Initializing the variable at the start of the function fixes this warning and ensures predictable behavior.
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/8c964b82a4e97ec7f25e17b803ee196009b38a57
- git.kernel.org/stable/c/b487a7754d874230299d5a9c2710ec4df8b2ed8a
- git.kernel.org/stable/c/c2026c6b603ebec52f55015496703fe79077accf
- git.kernel.org/stable/c/c65ee4d3be5df395e48afbcd0946dd5fce4338a9
- git.kernel.org/stable/c/d5b8f5f8d6fc09a8af5ed139c688660f578ed732
- git.kernel.org/stable/c/ef74ce5f0bc0e53ce702d8a794f3957884a26efc
Other references
Recent Use of Uninitialized Resource vulnerabilities
- 7.5 High severity
- 7.5 High severity
- 7.8 High severity
- 9.1 Critical severity
- 9.1 Critical severity
- 7.5 High severity
Spotted an error? Tell us.