VulnerabilityPublished 25 Jul 2026Updated 27 Jul 2026

CVE-2026-64445: Linux kernel · Out-of-bounds Read

Source GCVE Database

Authoritative record:CVE-2026-64445· High 8.8

Not known to be exploited · CVSS 8.8 High · fixed in d90b9f39f375c9826ef145605dfe97765d0ecb91 : patch Linux kernel soon.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score

8.8High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 24% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in d90b9f39f375c9826ef145605dfe97765d0ecb91, c9000c93078e5c0a5a651b077c0ec92a4bc7d580, a1fc19d61f661d47204f095b593de507884849f7 +5

CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack Vector: Adjacent
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: High
Availability: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Adjacent: The vulnerable component is bound to the network stack, but the attack is limited at the protocol level to a logically adjacent topology. This can mean an attack must be launched from the same shared physical (e.g., Bluetooth or IEEE 802.11) or logical (e.g., local IP subnet) network, or from within a secure or otherwise limited administrative domain (e.g., MPLS, secure VPN to an administrative network zone).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 25 Jul 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

ghsa-g74x-wr8m-rhmp

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected ≥ 554c0a3abf216c991c5ebddcdb2c08689ecd290b, < d90b9f39f375c9826ef145605dfe97765d0ecb91	Fixed in d90b9f39f375c9826ef145605dfe97765d0ecb91
LinuxLinux	Affected ≥ 554c0a3abf216c991c5ebddcdb2c08689ecd290b, < c9000c93078e5c0a5a651b077c0ec92a4bc7d580	Fixed in c9000c93078e5c0a5a651b077c0ec92a4bc7d580
LinuxLinux	Affected ≥ 554c0a3abf216c991c5ebddcdb2c08689ecd290b, < a1fc19d61f661d47204f095b593de507884849f7	Fixed in a1fc19d61f661d47204f095b593de507884849f7
LinuxLinux	Affected ≥ 554c0a3abf216c991c5ebddcdb2c08689ecd290b, < 665e1ecb68b4e8419604e70a33f02d1c8b0222c6	Fixed in 665e1ecb68b4e8419604e70a33f02d1c8b0222c6
LinuxLinux	Affected ≥ 554c0a3abf216c991c5ebddcdb2c08689ecd290b, < 87cccc2a767f17dcab71e3b9fe5ae29b5516c5ce	Fixed in 87cccc2a767f17dcab71e3b9fe5ae29b5516c5ce
LinuxLinux	Affected ≥ 554c0a3abf216c991c5ebddcdb2c08689ecd290b, < 64ec4192d9c10e96922245d4a6747304cc76b19d	Fixed in 64ec4192d9c10e96922245d4a6747304cc76b19d

AI-suggested

A fix has been applied to the Linux kernel rtl8723bs staging driver to address these vulnerabilities by adding proper length checks. Users should update their Linux kernel to a version that includes this fix. Since this is a kernel-level vulnerability, applying the official kernel update is the recommended remediation. Patch status is not explicitly confirmed in the provided data; check the Linux kernel vendor advisory for the exact fixed version and update accordingly.

Description

In the Linux kernel, the following vulnerability has been resolved: staging: rtl8723bs: fix WEP length underflow and OOB read in OnAuth() OnAuth() has two bugs in the shared-key authentication path. When the Privacy bit is set, rtw_wep_decrypt() is called without verifying that the frame is long enough to contain a valid WEP IV and ICV. Inside rtw_wep_decrypt(), length is computed as: length = len - WLAN_HDR_A3_LEN - iv_len and then passed as (length - 4) to crc32_le(). If len is less than WLAN_HDR_A3_LEN + iv_len + icv_len (32 bytes), length - 4 is negative and, after the implicit cast to size_t, causes crc32_le() to read far beyond the frame buffer. Add a minimum length check before accessing the IV field and calling the decryption path. When processing a seq=3 response, rtw_get_ie() stores the Challenge Text IE length in ie_len, but the subsequent memcmp() always reads 128 bytes regardless of ie_len. IEEE 802.11 mandates a challenge text of exactly 128 bytes; reject any IE whose length field differs, matching the check already applied to OnAuthClient().

Impact

These vulnerabilities can cause out-of-bounds reads in kernel memory during WEP decryption and Challenge Text IE processing, potentially leading to kernel crashes or information disclosure. The issues affect the shared-key authentication path in the rtl8723bs driver, which could impact devices using this driver for wireless connectivity.

Summary

The Linux kernel rtl8723bs staging driver had two vulnerabilities in the OnAuth() function's shared-key authentication path. When the Privacy bit is set, rtw_wep_decrypt() was called without verifying the frame length, leading to a length underflow and an out-of-bounds read in crc32_le(). Additionally, during processing of a seq=3 response, rtw_get_ie() stored the Challenge Text IE length but memcmp() read a fixed 128 bytes regardless of the actual length, violating IEEE 802.11 standards and causing an out-of-bounds read. The fixes add minimum length checks before accessing the IV field and enforce strict length validation on the Challenge Text IE.

CWE-125Out-of-bounds Read (opens in a new tab)
Base weaknessCWE Top 25 (2025): #8
The product reads data past the end, or before the beginning, of the intended buffer.
Implementation · Input Validation
Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
Architecture and Design · Language Selection
Use a language that provides appropriate memory abstractions.
OWASP Cheat Sheets
XML Security (opens in a new tab)
Mass Assignment (opens in a new tab)
OWASP ASVS 4.0.3
V13.3.1 (opens in a new tab)
V5.1.4 (opens in a new tab)
V5.1.3 (opens in a new tab)
Attack patterns
Overread Buffers (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 25 Jul 2026, 23:20 UTC

WeaknessesCWE-125

Technical details

References

Community reviews

Related threats