CVE-2026-23073

HIGHNVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-02-04. NVD baseline CVSS 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 0

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

wifi: rsi: Fix memory corruption due to not set vif driver data size

The struct ieee80211_vif contains trailing space for vif driver data, when struct ieee80211_vif is allocated, the total memory size that is allocated is sizeof(struct ieee80211_vif) + size of vif driver data. The size of vif driver data is set by each WiFi driver as needed.

The RSI911x driver does not set vif driver data size, no trailing space for vif driver data is therefore allocated past struct ieee80211_vif . The RSI911x driver does however use the vif driver data to store its vif driver data structure "struct vif_priv". An access to vif->drv_priv leads to access out of struct ieee80211_vif bounds and corruption of some memory.

In case of the failure observed locally, rsi_mac80211_add_interface() would write struct vif_priv *vif_info = (struct vif_priv *)vif->drv_priv; vif_info->vap_id = vap_idx. This write corrupts struct fq_tin member struct list_head new_flows . The flow = list_first_entry(head, struct fq_flow, flowchain); in fq_tin_reset() then reports non-NULL bogus address, which when accessed causes a crash.

The trigger is very simple, boot the machine with init=/bin/sh , mount devtmpfs, sysfs, procfs, and then do "ip link set wlan0 up", "sleep 1", "ip link set wlan0 down" and the crash occurs.

Fix this by setting the correct size of vif driver data, which is the size of "struct vif_priv", so that memory is allocated and the driver can store its driver data in it, instead of corrupting memory around it.

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
35(Track)
EG Risk 35/100SSVC: Track

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
Severity78% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
3%
KEV
Not listed

Published

February 4, 2026

Last Modified

June 17, 2026

Advisory Details (7)

Auto-updated Aug 2, 2026
No patch confirmed yet.
generic

wifi: rsi: Fix memory corruption due to not set vif driver data size - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/99129d80a5d4989ef8566f434f3589f60f28042b
generic

wifi: rsi: Fix memory corruption due to not set vif driver data size - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7c54d0c3e2cad4300be721ec2aecfcf8a63bc9f4
generic

wifi: rsi: Fix memory corruption due to not set vif driver data size - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7761d7801f40e61069b4df3db88b36d80d089f8a
generic

wifi: rsi: Fix memory corruption due to not set vif driver data size - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4f431d88ea8093afc7ba55edf4652978c5a68f33
generic

wifi: rsi: Fix memory corruption due to not set vif driver data size - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/49ef094fdbc3526e5db2aebb404b84f79c5603dc
generic

wifi: rsi: Fix memory corruption due to not set vif driver data size - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/31efbcff90884ea5f65bf3d1de01267db51ee3d1
generic

wifi: rsi: Fix memory corruption due to not set vif driver data size - kernel/git/stable/linux.git - Linux kernel stable tree

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

Patch Availability(21)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-nvidia-tegra-rt-5.15 (5.15.0.1057.57~20.04.1) @ focal2026-06-07ubuntu
ubuntulinux-tools-gcp-fips-5.15 (5.15.0.1105.95) @ jammy2026-06-07ubuntu
ubuntulinux-tools-nvidia-tegra-rt-5.15 (5.15.0.1057.57) @ jammy2026-06-07ubuntu
ubuntulinux-tools-realtime-5.15 (5.15.0.1104.108) @ jammy2026-06-07ubuntu
ubuntulinux-virtual-hwe-20.04-edge (5.15.0.176.186~20.04.1) @ focal2026-06-07ubuntu
ubuntulinux-tools-kvm-5.15 (5.15.0.1097.93) @ jammy2026-06-07ubuntu
ubuntulinux-tools-ibm-5.15 (5.15.0.1099.95) @ jammy2026-06-07ubuntu
ubuntulinux-tools-azure-edge (5.15.0.1110.119~20.04.1) @ focal2026-06-07ubuntu
ubuntulinux-tools-azure-fips-5.15 (5.15.0.1110.95) @ jammy2026-06-07ubuntu
ubuntulinux-tools-raspi-nolpae (5.15.0.1099.97) @ jammy2026-06-07ubuntu
ubuntulinux-xilinx-zynqmp-tools-5.15.0-1070 (5.15.0-1070.74) @ jammy2026-06-07ubuntu
ubuntulinux-virtual-6.8 (6.8.0-117.117) @ noble2026-06-07ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1054.57.1) @ noble2026-06-07ubuntu
ubuntulinux-tools-fips-6.8 (6.8.0-116.116+fips1) @ noble2026-06-07ubuntu
ubuntulinux-tools-gcp-edge (5.15.0.1106.115~20.04.1) @ focal2026-06-07ubuntu
ubuntulinux-tools-nvidia-tegra-rt-6.8 (6.8.0-1024.24) @ noble2026-06-07ubuntu
ubuntulinux-tools-nvidia-hwe-22.04-edge (6.8.0-1054.57~22.04.1) @ jammy2026-06-07ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1056.62) @ noble2026-06-07ubuntu
ubuntulinux-tools-azure-fips-6.8 (6.8.0-1059.65+fips1) @ noble2026-06-07ubuntu
ubuntulinux-tools-lowlatency-hwe-20.04-edge (5.15.0.175.185~20.04.1) @ focal2026-06-07ubuntu
linuxKernel @ 5.10.249—osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(5 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (48 versions)5.10.249-1—
linux-6.16.1.106-3~deb11u1 ... 6.1.159-1~deb11u1 (14 versions)6.1.162-1~deb11u1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (46 versions)6.1.162-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.69-1~bpo12+1 (10 versions)6.12.69-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.18~rc7-1~exp1 (96 versions)6.18.8-1—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(25)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 5× in last 7d / 26× 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 174 total refreshes for this CVE.

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

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-23073?
CVE-2026-23073 is a high vulnerability published on February 4, 2026. In the Linux kernel, the following vulnerability has been resolved: wifi: rsi: Fix memory corruption due to not set vif driver data size The struct ieee80211_vif contains trailing space for vif driver data, when struct ieee80211_vif is allocated, the total memory size that is allocated is…
When was CVE-2026-23073 disclosed?
CVE-2026-23073 was first published in the National Vulnerability Database on February 4, 2026, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-23073 actively exploited?
CVE-2026-23073 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 96.7% of all scored CVEs.
What is the CVSS score of CVE-2026-23073?
CVE-2026-23073 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-23073?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-23073, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-23073?

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

Start Free Scan →Browse All CVEs