CVE-2026-64030

HIGHPre-NVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-07-19. the CNA's CVSS baseline 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
Trending — 4 sources updated this week
8.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: 8.8Exploit: None knownExposed: 0

A fix is available — apply it.

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

wifi: mac80211: bounds-check link_id in ieee80211_ml_epcs

IEEE80211_MLE_STA_EPCS_CONTROL_LINK_ID is 0x000f, so link_id extracted from a PRIO_ACCESS ML element PER_STA_PROFILE subelement can be 0..15. sdata->link[] has IEEE80211_MLD_MAX_NUM_LINKS (15) entries (indices 0..14), making index 15 out-of-bounds.

A connected WiFi 7 AP can trigger this by sending an EPCS Enable Response action frame with a PER_STA_PROFILE subelement where link_id = 15. The unsolicited-notification path (dialog_token = 0) is reachable any time EPCS is already enabled, without any prior client request.

sdata->link[15] reads into the first word of sdata->activate_links_work (a wiphy_work whose embedded list_head is non-NULL after INIT_LIST_HEAD), so the NULL check on the result does not catch the invalid access. The garbage pointer is then passed to ieee80211_sta_wmm_params(), which dereferences link->sdata and crashes the kernel.

The same class of bug was fixed for ieee80211_ml_reconfiguration() by commit 162d331d833d ("wifi: mac80211: bounds-check link_id in ieee80211_ml_reconfiguration").

CVSS v3
8.8
EG Score
8.8(medium)
EG Risk
44(Track)
EG Risk 44/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
Severity88% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
15%
KEV
Not listed

Published

July 19, 2026

Last Modified

August 5, 2026

Advisory Details (3)

Auto-updated Jul 20, 2026
No patch confirmed yet.
generic

wifi: mac80211: bounds-check link_id in ieee80211_ml_epcs - kernel/git/stable/linux.git - Linux kernel stable tree

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

wifi: mac80211: bounds-check link_id in ieee80211_ml_epcs - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/863f1f02a3bd70dbd857b8ac4070292fde8cb4e2
generic

wifi: mac80211: bounds-check link_id in ieee80211_ml_epcs - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2d8379834800c30602f24c71ab7c40f5fe84d200

Vendor Advisories for CVE-2026-64030(1)

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

Patch Availability(5)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-oracle-7.0 (7.0.0-1008.8) @ resolute2026-08-30ubuntu
ubuntulinux-tools-azure-fde-7.0 (7.0.0-1009.9) @ resolute2026-08-30ubuntu
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1015.15) @ resolute2026-08-30ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1016.16) @ resolute2026-08-30ubuntu
ubuntulinux-tools-nvidia-hwe-26.04 (7.0.0-2016.16) @ resolute2026-08-30ubuntu

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

(1 across 1 ecosystem)
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (138 versions)7.0.12-1—

All Vendor Advisories

(5)

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 34× in last 7d / 164× 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 213 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-64030?
CVE-2026-64030 is a high vulnerability published on July 19, 2026. In the Linux kernel, the following vulnerability has been resolved: wifi: mac80211: bounds-check linkid in ieee80211ml_epcs IEEE80211MLESTAEPCSCONTROLLINKID is 0x000f, so link_id extracted from a PRIOACCESS ML element PERSTA_PROFILE subelement can be 0..15. sdata->link[] has IEEE80211MLDMAXNUMLINKS…
When was CVE-2026-64030 disclosed?
CVE-2026-64030 was first published in the National Vulnerability Database on July 19, 2026, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-64030 actively exploited?
CVE-2026-64030 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 85.2% of all scored CVEs.
What is the CVSS score of CVE-2026-64030?
CVE-2026-64030 has a CVSS v4.0 base score of 8.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-64030?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64030, 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-64030

Explore →

Is Your Infrastructure Affected by CVE-2026-64030?

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

Start Free Scan →Browse All CVEs