CVE-2026-74651
CVE CVE-2026-74651EUVD EUVD-2026-64588Published 2026-08-22T15:32:27.000ZLast changed 2026-08-25T05:41:09.000ZCVSS 8.1
What the advisory describes
In the Linux kernel, the following vulnerability has been resolved: staging: rtl8723bs: fix OOB read in rtw_get_wpa_ie() rtw_get_wpa_ie() reads bytes at fixed offsets into a vendor-specific information element without checking that the element is long enough, causing an out-of-bounds read for a short trailing IE. The function locates a vendor-specific IE (EID 221) with rtw_get_ie() and then compares a 4-byte OUI+type at pbuf + 2 and reads a 2-byte version word at pbuf + 6. Those accesses require the IE body to be at least 6 bytes, but rtw_get_ie() only guarantees that the element fits within the buffer; it does not enforce a minimum body length. A vendor-specific IE whose length byte is 0 to 5, placed at the end of the buffer, therefore makes these reads run past the end of the IE and past the end of the buffer itself. The buffer holds information elements taken from received management frames and from the IE blob passed to rtw_cfg80211_set_wpa_ie(), which is kmemdup'd to its exact length, so the read can run off the end of the allocation. The sibling helpers rtw_get_sec_ie(), rtw_get_wapi_ie() and rtw_get_wps_ie() in this file already reject too-short vendor-specific IEs before their OUI memcmp(); rtw_get_wpa_ie() was never brought in line with them, and needs a minimum of 6 rather than 4 bytes because of the version word. Add the missing length check.
Source: EUVD (ENISA), in the words of the advisory.
Products the advisory names
These come from the advisory itself, not from any check we performed.
- Linux — Linux patch: 7.1.9; 4.12; patch: 5.10.265; patch: 7.2; patch: 6.18.45; patch: 6.1.183; patch: 5.15.216; patch: 6.12.104; 554c0a3abf216c991c5ebddcdb2c08689ecd290b <0d19f0600fbb610c42f2a86f95c35706dc04691b; patch: 0; 554c0a3abf216c991c5ebddcdb2c08689ecd290b <c9068f82a0906b29c905e8788edb62c3208c7c8a; 554c0a3abf216c991c5ebddcdb2c08689ecd290b <01ab275f8f3e497a13ebbe4ded44ec0623bccde3; 554c0a3abf216c991c5ebddcdb2c08689ecd290b <e167a38a8a8f50f137721fef1a1fbba0f4588b5d; 554c0a3abf216c991c5ebddcdb2c08689ecd290b <4fc459c5cd8767ca4d9bf2f7becbd562639ba4d9; 554c0a3abf216c991c5ebddcdb2c08689ecd290b <1c3e23e78862493e8cf1adad02b10ffcb8b9921c; patch: 6.6.152; 554c0a3abf216c991c5ebddcdb2c08689ecd290b <b45be82387bf759931acdd21ca7dfe740f16eb97; 554c0a3abf216c991c5ebddcdb2c08689ecd290b <42c5a0d454aa5b54fec17162d9a1f8c30f8af45a
The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.
Carried in the product catalogue
An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.
- Linux — Linux
Does this concern one of your customers?
This page cannot answer that — it does not know your estate. Whoever has recorded their environments gets the answer the morning after publication, together with a paragraph they can forward to the customer unedited.
Try it for 28 daysPatchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.