CVE-2026-90016

HIGHPre-NVD 7.17.1—
EchelonGraph scoreHIGH confidence

Score 7.1 from GitHub Security Advisory (severity: HIGH) published 2026-09-16. A secondary CVSS source baseline 7.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
7.1EG
EchelonGraph verdictPlan mitigationSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 7.1Exploit: None knownExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

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.

CVSS v3
7.1
EG Score
7.1HIGHhigh confidence
EG Risk
37
EG Risk 37/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity71% × 45%
Exploitation0% × 40%
Automatability30% × 15%
CISA SSVC: Track at low or medium mission impact; Track or Attend at high (mission-essential systems).
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
0.4%
EPSS %ILE
31st
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track or Attend at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

September 16, 2026

Last Modified

October 3, 2026

Advisory Details (3)

Auto-updated Sep 16, 2026
No patch confirmed yet.
generic

staging: rtl8723bs: fix OOB read in rtw_restruct_wmm_ie() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/fd19b8895f8a91087e8a62f1e27b128025dabb95
generic

staging: rtl8723bs: fix OOB read in rtw_restruct_wmm_ie() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4420cc71841b50e31a7868ef7acb011c0e08d294
generic

staging: rtl8723bs: fix OOB read in rtw_restruct_wmm_ie() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/28a289beaf226b30b1e6e7d7b1a2946fe2d6e852

Vendor Advisories for CVE-2026-90016(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 7.2~rc7-1~exp1 (360 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (183 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (179 versions)
  • every version up to 7.2.6-1: fixed in 7.2.6-1
—

Data Freshness Timeline

(refreshed 41× in last 7d / 112× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 112 total refreshes for this CVE.

  1. 2026-10-05 01:05 UTCEG score recompute
  2. 2026-10-05 01:05 UTCVendor advisory
  3. 2026-10-05 01:05 UTCGHSA enrichment
  4. 2026-10-04 23:22 UTCEPSS rescore
  5. 2026-10-04 12:29 UTCVendor advisory
  6. 2026-10-04 12:29 UTCGHSA enrichment
  7. 2026-10-04 00:02 UTCEG score recompute
  8. 2026-10-04 00:02 UTCVendor advisory
  9. 2026-10-04 00:01 UTCGHSA enrichment
  10. 2026-10-03 11:33 UTCVendor advisory
  11. 2026-10-03 11:33 UTCGHSA enrichment
  12. 2026-10-03 08:39 UTCVendor advisory
  13. 2026-10-03 08:39 UTCGHSA enrichment
  14. 2026-10-02 19:48 UTCEG score recompute
  15. 2026-10-02 19:48 UTCVendor advisory
  16. 2026-10-02 19:48 UTCGHSA enrichment
  17. 2026-10-02 07:20 UTCEG score recompute
  18. 2026-10-02 07:20 UTCVendor advisory
  19. 2026-10-02 07:20 UTCGHSA enrichment
  20. 2026-10-01 19:51 UTCEPSS rescore
  21. 2026-10-01 18:53 UTCVendor advisory
  22. 2026-10-01 18:53 UTCGHSA enrichment
  23. 2026-10-01 05:26 UTCVendor advisory
  24. 2026-10-01 05:25 UTCGHSA enrichment
  25. 2026-09-30 16:58 UTCEG score recompute
Show 75 more
  1. 2026-09-30 16:58 UTCVendor advisory
  2. 2026-09-30 16:58 UTCGHSA enrichment
  3. 2026-09-30 15:04 UTCEPSS rescore
  4. 2026-09-30 03:54 UTCVendor advisory
  5. 2026-09-30 03:54 UTCGHSA enrichment
  6. 2026-09-29 15:27 UTCEG score recompute
  7. 2026-09-29 15:27 UTCVendor advisory
  8. 2026-09-29 15:27 UTCGHSA enrichment
  9. 2026-09-29 02:57 UTCEG score recompute
  10. 2026-09-29 02:57 UTCVendor advisory
  11. 2026-09-29 02:57 UTCGHSA enrichment
  12. 2026-09-28 14:29 UTCEG score recompute
  13. 2026-09-28 14:29 UTCVendor advisory
  14. 2026-09-28 14:29 UTCGHSA enrichment
  15. 2026-09-28 13:52 UTCEPSS rescore
  16. 2026-09-28 13:52 UTCEPSS rescore
  17. 2026-09-28 01:56 UTCEG score recompute
  18. 2026-09-28 01:56 UTCVendor advisory
  19. 2026-09-28 01:56 UTCGHSA enrichment
  20. 2026-09-27 13:49 UTCEPSS rescore
  21. 2026-09-27 13:29 UTCVendor advisory
  22. 2026-09-27 13:28 UTCGHSA enrichment
  23. 2026-09-27 00:57 UTCEG score recompute
  24. 2026-09-27 00:57 UTCVendor advisory
  25. 2026-09-27 00:57 UTCGHSA enrichment
  26. 2026-09-26 15:59 UTCEPSS rescore
  27. 2026-09-26 12:29 UTCEG score recompute
  28. 2026-09-26 12:29 UTCVendor advisory
  29. 2026-09-26 12:29 UTCGHSA enrichment
  30. 2026-09-26 00:02 UTCVendor advisory
  31. 2026-09-26 00:01 UTCGHSA enrichment
  32. 2026-09-25 11:29 UTCGHSA enrichment
  33. 2026-09-24 23:01 UTCEG score recompute
  34. 2026-09-24 23:01 UTCVendor advisory
  35. 2026-09-24 23:01 UTCGHSA enrichment
  36. 2026-09-24 14:04 UTCEPSS rescore
  37. 2026-09-24 10:29 UTCVendor advisory
  38. 2026-09-24 10:29 UTCGHSA enrichment
  39. 2026-09-23 22:01 UTCEG score recompute
  40. 2026-09-23 22:01 UTCVendor advisory
  41. 2026-09-23 22:01 UTCGHSA enrichment
  42. 2026-09-23 17:54 UTCEPSS rescore
  43. 2026-09-23 09:34 UTCVendor advisory
  44. 2026-09-23 09:34 UTCGHSA enrichment
  45. 2026-09-22 21:06 UTCEG score recompute
  46. 2026-09-22 21:06 UTCVendor advisory
  47. 2026-09-22 21:06 UTCGHSA enrichment
  48. 2026-09-22 16:01 UTCEPSS rescore
  49. 2026-09-22 08:39 UTCEG score recompute
  50. 2026-09-22 08:39 UTCVendor advisory
  51. 2026-09-22 08:38 UTCGHSA enrichment
  52. 2026-09-21 21:09 UTCEPSS rescore
  53. 2026-09-21 20:11 UTCVendor advisory
  54. 2026-09-21 20:11 UTCGHSA enrichment
  55. 2026-09-21 07:43 UTCEG score recompute
  56. 2026-09-21 07:43 UTCVendor advisory
  57. 2026-09-21 07:43 UTCGHSA enrichment
  58. 2026-09-20 20:16 UTCEPSS rescore
  59. 2026-09-20 19:15 UTCVendor advisory
  60. 2026-09-20 19:15 UTCGHSA enrichment
  61. 2026-09-20 06:48 UTCVendor advisory
  62. 2026-09-20 06:47 UTCGHSA enrichment
  63. 2026-09-19 18:08 UTCEG score recompute
  64. 2026-09-19 18:08 UTCVendor advisory
  65. 2026-09-19 18:07 UTCGHSA enrichment
  66. 2026-09-19 05:39 UTCEG score recompute
  67. 2026-09-19 05:39 UTCVendor advisory
  68. 2026-09-19 05:39 UTCGHSA enrichment
  69. 2026-09-18 19:28 UTCEPSS rescore
  70. 2026-09-18 17:12 UTCVendor advisory
  71. 2026-09-18 17:12 UTCGHSA enrichment
  72. 2026-09-18 04:44 UTCEG score recompute
  73. 2026-09-18 04:44 UTCVendor advisory
  74. 2026-09-18 04:44 UTCGHSA enrichment
  75. 2026-09-17 19:32 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-90016?
CVE-2026-90016 is a high vulnerability published on September 16, 2026. In the Linux kernel, the following vulnerability has been resolved: staging: rtl8723bs: fix OOB read in rtwrestructwmm_ie() rtwrestructwmmie() scans inie for a WMM IE with: while (i < in_len) { ... if (i + 5 < inlen && inie[i] == 0xDD && ...) { ... break; } i += (in_ie[i + 1] + 2); / to the next IE…
When was CVE-2026-90016 disclosed?
CVE-2026-90016 was first published on September 16, 2026, with the most recent update on October 3, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-90016 actively exploited?
CVE-2026-90016 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (31st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-90016?
CVE-2026-90016 has a CVSS base score of 7.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-90016?
No fix for CVE-2026-90016 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-90016 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-90016

Explore →

Is Your Infrastructure Affected by CVE-2026-90016?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.