Skip to main content
VulnerabilityPublished Updated

CVE-2026-90016: Linux kernel · staging: rtl8723bs: fix OOB read in rtw_restruct_wmm_ie()

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-90016· High 7.1

Not known to be exploited · CVSS 7.1 High · fixed in fd19b8895f8a91087e8a62f1e27b128025dabb95 : patch Linux kernel soon.

Data as of 30 Oct 2026, 16:33 UTC

CVSS 3.1 base score
7.1High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (Linux)CVSS 3.17.1
Patch
Available – fixed in fd19b8895f8a91087e8a62f1e27b128025dabb95, e63b72c5d7336981dfc05e5cb92becff29dfea00, a8d76480d1abbbf617c2d6d9f60bf95ab45cff04 +5
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 16 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 554c0a3abf216c991c5ebddcdb2c08689ecd290b, < fd19b8895f8a91087e8a62f1e27b128025dabb95
Fixed in
  • fd19b8895f8a91087e8a62f1e27b128025dabb95
LinuxLinuxAffected
  • ≥ 554c0a3abf216c991c5ebddcdb2c08689ecd290b, < e63b72c5d7336981dfc05e5cb92becff29dfea00
Fixed in
  • e63b72c5d7336981dfc05e5cb92becff29dfea00
LinuxLinuxAffected
  • ≥ 554c0a3abf216c991c5ebddcdb2c08689ecd290b, < a8d76480d1abbbf617c2d6d9f60bf95ab45cff04
Fixed in
  • a8d76480d1abbbf617c2d6d9f60bf95ab45cff04
LinuxLinuxAffected
  • ≥ 554c0a3abf216c991c5ebddcdb2c08689ecd290b, < 716850842d2f103f915fe7c857ff1a0a036491b4
Fixed in
  • 716850842d2f103f915fe7c857ff1a0a036491b4
LinuxLinuxAffected
  • ≥ 554c0a3abf216c991c5ebddcdb2c08689ecd290b, < 55034fa38bd8b302ceb32c15e8a98298f56f629b
Fixed in
  • 55034fa38bd8b302ceb32c15e8a98298f56f629b
LinuxLinuxAffected
  • ≥ 554c0a3abf216c991c5ebddcdb2c08689ecd290b, < 4420cc71841b50e31a7868ef7acb011c0e08d294
Fixed in
  • 4420cc71841b50e31a7868ef7acb011c0e08d294

Description

In the Linux kernel, the following vulnerability has been resolved: staging: rtl8723bs: fix OOB read in rtw_restruct_wmm_ie() rtw_restruct_wmm_ie() scans in_ie for a WMM IE with: while (i < in_len) { ... if (i + 5 < in_len && in_ie[i] == 0xDD && ...) { ... break; } i += (in_ie[i + 1] + 2); /* to the next IE element */ } When the "i + 5 < in_len" match check fails simply because i is within 5 bytes of the end of the buffer (i.e. no WMM IE was found near the tail of in_ie), execution falls through to "i += (in_ie[i + 1] + 2)", which reads in_ie[i + 1]. If i == in_len - 1 at that point, this is a 1-byte out-of-bounds read of an attacker-influenced IE buffer built from association/scan data. Commit a75281626fc8f ("staging: rtl8723bs: fix potential out-of-bounds read in rtw_restruct_wmm_ie") added the "i + 5 < in_len" guard to the match condition itself, but did not add an equivalent guard before the fallthrough advance, so the same class of OOB read remained reachable through the non-matching path. Add an explicit bounds check before advancing to the next IE.

References

Community reviews

Loading reviews…