CVE-2026-90017

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_action_frame_parse()

rtw_action_frame_parse() takes a frame_len parameter but never actually checks it before indexing into the frame body:

const u8 *frame_body = frame + sizeof(struct ieee80211_hdr_3addr); ... c = frame_body[0]; ... a = frame_body[1];

frame_body already points 24 bytes (sizeof(struct ieee80211_hdr_3addr)) into frame, so reading frame_body[0] and frame_body[1] requires frame_len >= 26. A management action frame shorter than that (e.g. exactly 24 bytes, the minimum a malicious peer can send) causes a 1-2 byte out-of-bounds read.

This is reachable from rtw_cfg80211_monitor_if_xmit_entry() and cfg80211_rtw_mgmt_tx() in ioctl_cfg80211.c, both of which pass attacker/user-influenced frame buffers and lengths straight through.

Add the missing length check before frame_body is dereferenced.

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
32nd
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

September 16, 2026

Advisory Details (8)

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

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

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

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

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

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

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

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

https://git.kernel.org/stable/c/310aaa8058d19cc431aedac0f5bb814e84479393
generic

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

https://git.kernel.org/stable/c/15081ff835b29e456da29303b32efc436df04695
generic

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

https://git.kernel.org/stable/c/1410bce22351ba15d8e58287cbf09d55d7f21fc9
generic

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

https://git.kernel.org/stable/c/136f9a3ab87ded8aaf081425cfb2059659dd9023
generic

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

https://git.kernel.org/stable/c/0b7f64c7bb9664777168768c6b44affb07dcbf24

Vendor Advisories for CVE-2026-90017(2)

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

Affected Packages

(4 across 3 ecosystems)
Debian:12(2)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 7.2~rc7-1~exp1 (360 versions)
  • every version on: no fix on record
—
linux-6.126.12.100-1~deb12u1, 6.12.101-1~deb12u1, 6.12.107-1~deb12u1
  • every version up to 6.12.111-1~deb12u1: fixed in 6.12.111-1~deb12u1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 6.12.96-1 (35 versions)
  • every version up to 6.12.111-1: fixed in 6.12.111-1
—
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 40× in last 7d / 111× 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 111 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-90017?
CVE-2026-90017 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 rtwactionframe_parse() rtwactionframeparse() takes a framelen parameter but never actually checks it before indexing into the frame body: const u8 *framebody = frame + sizeof(struct…
When was CVE-2026-90017 disclosed?
CVE-2026-90017 was first published on September 16, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-90017 actively exploited?
CVE-2026-90017 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (32nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-90017?
CVE-2026-90017 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-90017?
No fix for CVE-2026-90017 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-90017 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-90017

Explore →

Is Your Infrastructure Affected by CVE-2026-90017?

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