staging: rtl8723bs: fix OOB read in rtw_get_wpa_ie()
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 5.10.265, 5.15.216, 6.1.183, 6.6.152, 6.12.104, and 2 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- Linux Linux
From 554c0a3abf216c991c5ebddcdb2c08689ecd290b · fixed in 4fc459c5cd8767ca4d9bf2f7becbd562639ba4d9; From 554c0a3abf216c991c5ebddcdb2c08689ecd290b · fixed in b45be82387bf759931acdd21ca7dfe740f16eb97; From 554c0a3abf216c991c5ebddcdb2c08689ecd290b · fixed in c9068f82a0906b29c905e8788edb62c3208c7c8a; From 554c0a3abf216c991c5ebddcdb2c08689ecd290b · fixed in 0d19f0600fbb610c42f2a86f95c35706dc04691b; From 554c0a3abf216c991c5ebddcdb2c08689ecd290b · fixed in 42c5a0d454aa5b54fec17162d9a1f8c30f8af45a; From 554c0a3abf216c991c5ebddcdb2c08689ecd290b · fixed in e167a38a8a8f50f137721fef1a1fbba0f4588b5d; From 554c0a3abf216c991c5ebddcdb2c08689ecd290b · fixed in 01ab275f8f3e497a13ebbe4ded44ec0623bccde3; From 554c0a3abf216c991c5ebddcdb2c08689ecd290b · fixed in 1c3e23e78862493e8cf1adad02b10ffcb8b9921c
- Linux Linux
4.12
- KernelLinux
From 4.12.0 · fixed in 5.10.265; From 5.11.0 · fixed in 5.15.216; From 5.16.0 · fixed in 6.1.183; From 6.2.0 · fixed in 6.6.152; From 6.7.0 · fixed in 6.12.104; From 6.13.0 · fixed in 6.18.45; From 6.19.0 · fixed in 7.1.9
References 8
git.kernel.org
- stable/c/4fc459c5cd8767ca4d9bf2f7becbd562639ba4d9
- stable/c/b45be82387bf759931acdd21ca7dfe740f16eb97
- stable/c/c9068f82a0906b29c905e8788edb62c3208c7c8a
- stable/c/0d19f0600fbb610c42f2a86f95c35706dc04691b
- stable/c/42c5a0d454aa5b54fec17162d9a1f8c30f8af45a
- stable/c/e167a38a8a8f50f137721fef1a1fbba0f4588b5d
- stable/c/01ab275f8f3e497a13ebbe4ded44ec0623bccde3
- stable/c/1c3e23e78862493e8cf1adad02b10ffcb8b9921c