CVE-2026-64442
Medium
Elevated severity or exploit probability.
CVSS breakdown
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H
| Attack Vector | A | Adjacent |
| Attack Complexity | L | Low |
| Privileges Required | N | None |
| User Interaction | N | None |
| Scope | U | Unchanged |
| Confidentiality | H | High |
| Integrity | N | None |
| Availability | H | High |
Timeline
- 2026-07-25 — Published (NVD)
- 2026-09-03 — Last modified (NVD)
Description
In the Linux kernel, the following vulnerability has been resolved: staging: rtl8723bs: fix OOB reads in IE loops in issue_assocreq() and join_cmd_hdl() Two IE parsing loops are missing the header bounds checks before they dereference pIE->length: - issue_assocreq() walks pmlmeinfo->network.ies to build the association request. If the stored IE data ends with only an element_id byte and no length byte, pIE->length is read one byte past the end of the buffer. - join_cmd_hdl() walks pnetwork->ies during station join and has the same problem under the same conditions. Both buffers are filled from AP beacon and probe-response frames, so a malicious AP that sends a truncated final IE can trigger the issue. Apply the two-guard pattern established in update_beacon_info(): 1. Break if fewer than sizeof(*pIE) bytes remain. 2. Break if the IE's declared data extends past the buffer end.
Affected
References
- https://git.kernel.org/stable/c/402f13ec95945f34a210b28df1f8740d3d4a58c5
- https://git.kernel.org/stable/c/4c21eec80cf502d9ea18e0b946246b2376452786
- https://git.kernel.org/stable/c/605ebd94d0f469204f3c9f2f84acc71e43e2780f
- https://git.kernel.org/stable/c/a830bdc82461353bf7b1f8a2ad2689bf5d2de444
- https://git.kernel.org/stable/c/ad2637c46ef8b8ae0894372a2d39fdfcdc420a1e
- https://git.kernel.org/stable/c/bc881c9915c4468747d0ca5fd1abd7b313cfb0f4
- https://git.kernel.org/stable/c/c38d16b1ffac385c9e4b38447cd5c46af1114b58
- https://git.kernel.org/stable/c/ef61d628dfad38fead1fd2e08979ae9126d011d5