CVE-2026-90018staging: rtl8723bs: fix OOB read / stack overflow in rtw_get_wps_attr()
- 8.8HighCVSS base score
- 0.45%Exploitation in 30 daysEPSS · top 61% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
In the Linux kernel, the following vulnerability has been resolved: staging: rtl8723bs: fix OOB read / stack overflow in rtw_get_wps_attr() rtw_get_wps_attr() walks WPS attributes inside a WPS IE taken from a wireless management frame. For each candidate attribute it only checks that the fixed 4-byte attribute header (2-byte ID + 2-byte length) fits inside the IE: if (attr_ptr + 4 > wps_ie + wps_ielen) break; u16 attr_id = get_unaligned_be16(attr_ptr); u16 attr_data_len = get_unaligned_be16(attr_ptr + 2); u16 attr_len = attr_data_len + 4; attr_data_len (and therefore attr_len) is read directly from the wire and is never checked against the remaining bytes in the IE before being used as the size of: memcpy(buf_attr, attr_ptr, attr_len); Since attr_len is fully attacker controlled (0 to 65535+4), this is both a heap OOB read of wps_ie, and, more seriously, a stack buffer overflow at several call sites where buf_attr is a single-byte stack variable, e.g. rtw_get_wps_attr_content()'s callers passing WPS_ATTR_SELECTED_REGISTRAR into a stack "u8 sr"/"u8 selected_registrar" (drivers/staging/rtl8723bs/os_dep/ioctl_cfg80211.c, drivers/staging/rtl8723bs/core/rtw_mlme_ext.c). A crafted WPS IE in a beacon or probe response processed during scanning can therefore smash the stack of the parsing thread. rtw_get_wps_attr_content() itself has no independent length check and simply trusts the attr_len it gets back from rtw_get_wps_attr(), so fixing the bound here also fixes that caller. The "attr_ptr + 4 > wps_ie + wps_ielen" header check above was added by commit 1463ca3ec6601 ("staging: rtl8723bs: fix OOB reads in rtw_get_sec_ie(), rtw_get_wapi_ie(), and rtw_get_wps_attr()"), which bounded the fixed header but never extended the check to cover the variable-length attribute data that follows it. Add that missing check before attr_len is used as a memcpy() length or accepted as a match.
Timeline
ID reserved
By Linux
- 5 days later
· 5 days later
Published
- 33 days later
· 33 days later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| LinuxCNA (assigner) | 3.1 | High8.8 | CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVDNVD · Received | 3.1 | High8.8 | CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
- EPSS (exploitation in 30 days)
- 0.45% · top 61% of all CVEs (16 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 8.8.
Affected products
- affected 554c0a3abf216c991c5ebddcdb2c08689ecd290b – < 931640dfcb8cfa08f6cfb46229716d8072356420
- affected 554c0a3abf216c991c5ebddcdb2c08689ecd290b – < 3a6457ebf39080b87c712657fdb38f34a24fc3ff
- affected 554c0a3abf216c991c5ebddcdb2c08689ecd290b – < fd5e24ea8373347d0352f153a66e8647337d1b10
- affected 554c0a3abf216c991c5ebddcdb2c08689ecd290b – < a53d1ac9ce63db07943b2b2248111003851fb00f
- affected 554c0a3abf216c991c5ebddcdb2c08689ecd290b – < ff61aa3289355dafa811550a1764691cd1f5d33b
- affected 554c0a3abf216c991c5ebddcdb2c08689ecd290b – < 34f51d196c43a42046d229de5e79025d5ca553ca
- affected 554c0a3abf216c991c5ebddcdb2c08689ecd290b – < 99aa998dec83ba180822f70e6d48a514fc81c20d
- affected 4.12
- unaffected < 4.12
- unaffected 5.15.221 – ≤ 5.15.*
- unaffected 6.1.188 – ≤ 6.1.*
- unaffected 6.6.157 – ≤ 6.6.*
- unaffected 6.12.110 – ≤ 6.12.*
- unaffected 6.18.51 – ≤ 6.18.*
- unaffected 7.2.5 – ≤ 7.2.*
- unaffected 7.3 – ≤ *
References
References7
- https://git.kernel.org/stable/c/931640dfcb8cfa08f6cfb46229716d8072356420 (opens in a new tab)
- https://git.kernel.org/stable/c/3a6457ebf39080b87c712657fdb38f34a24fc3ff (opens in a new tab)
- https://git.kernel.org/stable/c/fd5e24ea8373347d0352f153a66e8647337d1b10 (opens in a new tab)
- https://git.kernel.org/stable/c/a53d1ac9ce63db07943b2b2248111003851fb00f (opens in a new tab)
- https://git.kernel.org/stable/c/ff61aa3289355dafa811550a1764691cd1f5d33b (opens in a new tab)
- https://git.kernel.org/stable/c/34f51d196c43a42046d229de5e79025d5ca553ca (opens in a new tab)
- https://git.kernel.org/stable/c/99aa998dec83ba180822f70e6d48a514fc81c20d (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-80626 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-90018)Record last updated .