CVE-2026-64440
Last modified
CVE-2026-64440 is a high-severity vulnerability rated 8.1/10 on the CVSS scale. In the Linux kernel, the following vulnerability has been resolved: staging: rtl8723bs: fix OOB write in HT_caps_handler() HT_caps_handler() iterates pIE->length bytes and writes into HT_caps.u.HT_cap[], which is a fixed 26-byte array (sizeof struct HT_caps_element). Because pIE->length is a raw u8 from an over-the-air 802.11 AssocResponse frame and is never validated, a malicious AP can set it up to 255, causing up to 229 bytes of out-of-bounds writes into adjacent fields of struct mlme_ext_info. Truncate the iteration count to the size of HT_caps.u.HT_cap using umin() so that data from a longer-than-expected IE is silently ignored rather than written out of bounds, preserving interoperability with APs that pad the element. EPSS estimates a 0.27% chance of exploitation in the next 30 days.
Description
In the Linux kernel, the following vulnerability has been resolved: staging: rtl8723bs: fix OOB write in HT_caps_handler() HT_caps_handler() iterates pIE->length bytes and writes into HT_caps.u.HT_cap[], which is a fixed 26-byte array (sizeof struct HT_caps_element). Because pIE->length is a raw u8 from an over-the-air 802.11 AssocResponse frame and is never validated, a malicious AP can set it up to 255, causing up to 229 bytes of out-of-bounds writes into adjacent fields of struct mlme_ext_info. Truncate the iteration count to the size of HT_caps.u.HT_cap using umin() so that data from a longer-than-expected IE is silently ignored rather than written out of bounds, preserving interoperability with APs that pad the element. An early return on oversized IEs was considered but rejected: it would bypass the pmlmeinfo->HT_caps_enable = 1 assignment that precedes the loop, silently disabling HT mode for APs that append extra bytes to the HT Capabilities IE.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Linux | Linux Kernel | >= 4.12, < 5.15.212 | — |
| Linux | Linux Kernel | >= 5.16, < 6.1.178 | — |
| Linux | Linux Kernel | >= 6.2, < 6.6.145 | — |
| Linux | Linux Kernel | >= 6.7, < 6.12.96 | — |
| Linux | Linux Kernel | >= 6.13, < 6.18.39 | — |
| Linux | Linux Kernel | >= 6.19, < 7.1.4 | — |
| Linux | Linux Kernel | 7.2 | Rc1 |
References
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2026-64440?
How severe is CVE-2026-64440?
How do I fix CVE-2026-64440?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-64435In the Linux kernel, the following vulnerability has been re…8.2
- CVE-2026-64436In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2026-64437In the Linux kernel, the following vulnerability has been re…8.8
- CVE-2026-64438In the Linux kernel, the following vulnerability has been re…8.8
- CVE-2026-64439In the Linux kernel, the following vulnerability has been re…9.8
- CVE-2026-6444A flaw exists in the FlashArray Purity management interface …8.6
- CVE-2026-64441In the Linux kernel, the following vulnerability has been re…8.8
- CVE-2026-64442In the Linux kernel, the following vulnerability has been re…8.1
- CVE-2026-64443In the Linux kernel, the following vulnerability has been re…8.1
- CVE-2026-64444In the Linux kernel, the following vulnerability has been re…8.1
- CVE-2026-64445In the Linux kernel, the following vulnerability has been re…8.8
- CVE-2026-64446In the Linux kernel, the following vulnerability has been re…7.8
Are you affected by CVE-2026-64440?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
