CVE-2026-64443: Linux kernel · staging: rtl8723bs: fix OOB read in update_beacon_info() IE loop
Source GCVE Database
Not known to be exploited · CVSS 8.1 High · fixed in ed51de4a86e173c3b0ef78e039c2e49e08b11f16 : patch Linux kernel soon.
Data as of 26 Oct 2026, 13:47 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 20% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in ed51de4a86e173c3b0ef78e039c2e49e08b11f16, bd953d52d587d42365e399b96c52dbdb13032070, b5cc2f999927f69723ca53f1f2a3aa37dbeda907 +4
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:HExploitation 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.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
AI-suggested
A fix for this vulnerability has been implemented in the Linux kernel rtl8723bs staging driver by adding proper bounds checks in the IE parsing loop. Users should apply the official kernel updates that include this patch once available.
Description
In the Linux kernel, the following vulnerability has been resolved: staging: rtl8723bs: fix OOB read in update_beacon_info() IE loop The IE parsing loop in update_beacon_info() advances by (pIE->length + 2) each iteration but only guards on i < len. When a malicious AP sends a Beacon whose last IE has only one byte remaining in the frame (the element_id byte lands at len-1), the loop reads pIE->length from one byte past the allocated receive buffer. Additionally, even when the header bytes are in bounds, pIE->length itself can extend the data window beyond len, passing a truncated IE to the handler functions. Add two guards at the top of the loop body: 1. Break if fewer than sizeof(*pIE) bytes remain (can't read header). 2. Break if the IE's declared data extends past len. Also replace i += (pIE->length + 2) with i += sizeof(*pIE) + pIE->length for consistency with the sizeof(*pIE) guards added above.
References
- nvd.nist.gov/vuln/detail/CVE-2026-64443 (opens in a new tab)
- git.kernel.org/stable/c/5e8db4cff5b45c7c4edc8ae3f302027c3bb32b25 (opens in a new tab)
- git.kernel.org/stable/c/69f174a0673b6b7a29b851adb60bc450cdc0ecc4 (opens in a new tab)
- git.kernel.org/stable/c/6dd5e8c3011ebabf417257d7f07901a7c4311539 (opens in a new tab)
- git.kernel.org/stable/c/9193c34f75fd9e1ea8a590d7cced464c3380dc29 (opens in a new tab)
- git.kernel.org/stable/c/b5cc2f999927f69723ca53f1f2a3aa37dbeda907 (opens in a new tab)
- git.kernel.org/stable/c/bd953d52d587d42365e399b96c52dbdb13032070 (opens in a new tab)
- git.kernel.org/stable/c/ed51de4a86e173c3b0ef78e039c2e49e08b11f16 (opens in a new tab)