CVE-2026-64445

HIGHPre-NVD 8.88.8
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 87% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 5 sources updated this week
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.8Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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().

CVSS v3
8.8
EG Score
8.8(medium)
EG Risk
44(Track)
EG Risk 44/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity88% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
24%
KEV
Not listed

Published

July 25, 2026

Last Modified

July 27, 2026

Advisory Details (8)

Auto-updated Jul 27, 2026
No patch confirmed yet.
generic

staging: rtl8723bs: fix WEP length underflow and OOB read in OnAuth() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/d90b9f39f375c9826ef145605dfe97765d0ecb91
generic

staging: rtl8723bs: fix WEP length underflow and OOB read in OnAuth() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/c9000c93078e5c0a5a651b077c0ec92a4bc7d580
generic

staging: rtl8723bs: fix WEP length underflow and OOB read in OnAuth() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/a1fc19d61f661d47204f095b593de507884849f7
generic

staging: rtl8723bs: fix WEP length underflow and OOB read in OnAuth() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/87cccc2a767f17dcab71e3b9fe5ae29b5516c5ce
generic

staging: rtl8723bs: fix WEP length underflow and OOB read in OnAuth() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/665e1ecb68b4e8419604e70a33f02d1c8b0222c6
generic

staging: rtl8723bs: fix WEP length underflow and OOB read in OnAuth() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/64ec4192d9c10e96922245d4a6747304cc76b19d
generic

staging: rtl8723bs: fix WEP length underflow and OOB read in OnAuth() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3e44a7665f3abd320a80d9c64ee4a93317041b8b
generic

staging: rtl8723bs: fix WEP length underflow and OOB read in OnAuth() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1f6c9d255bdda41216b6e34c96aa2b1abee0bb84

Vendor Advisories for CVE-2026-64445(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Data Freshness Timeline

(refreshed 15× in last 7d / 15× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-27 14:14 UTCEPSS rescore
  2. 2026-07-27 05:26 UTCEG score recompute
  3. 2026-07-27 05:26 UTCGHSA enrichment
  4. 2026-07-27 05:13 UTCEG score recompute 8.80
  5. 2026-07-27 05:13 UTCGHSA enrichment
  6. 2026-07-27 05:12 UTCMITRE cvelistV5CVSS v3 → 8.8 · severity → HIGH
  7. 2026-07-26 14:54 UTCEPSS rescore
  8. 2026-07-26 14:54 UTCEPSS rescore
  9. 2026-07-26 02:47 UTCEG score recompute
  10. 2026-07-26 02:47 UTCGHSA enrichment
  11. 2026-07-25 14:18 UTCEPSS rescore
  12. 2026-07-25 14:18 UTCEPSS rescore
  13. 2026-07-25 10:39 UTCNVD update
  14. 2026-07-25 09:26 UTCEG score recompute
  15. 2026-07-25 09:21 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-64445?
CVE-2026-64445 is a high vulnerability published on July 25, 2026. 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, rtwwepdecrypt() is called without verifying that the frame is long…
When was CVE-2026-64445 disclosed?
CVE-2026-64445 was first published in the National Vulnerability Database on July 25, 2026, with the most recent update on July 27, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-64445 actively exploited?
CVE-2026-64445 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 76.1% of all scored CVEs.
What is the CVSS score of CVE-2026-64445?
CVE-2026-64445 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-64445?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64445, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-64445

Explore →

Is Your Infrastructure Affected by CVE-2026-64445?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.