CVE-2026-64117

HIGHPre-NVD 8.88.8
EchelonGraph scoreHIGH confidence

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-07-19. a secondary CVSS source baseline 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
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: capture fast-RX rate before mesh reuses skb->cb

ieee80211_invoke_fast_rx() reads RX status through IEEE80211_SKB_RXCB(skb), which aliases the same skb->cb storage that ieee80211_rx_mesh_data() reuses as IEEE80211_TX_INFO. In the unicast forward path, mesh_data does:

info = IEEE80211_SKB_CB(fwd_skb); memset(info, 0, sizeof(*info));

on the same skb the caller still names via rx->skb, then either queues the skb for TX (success) or kfree_skb()'s it (no-route) before returning RX_QUEUED. The caller's RX_QUEUED arm then calls sta_stats_encode_rate(status) on memory that is either zeroed (success path) or freed (no-route path). The latter is KASAN slab-use-after-free in ieee80211_prepare_and_rx_handle.

Fix by encoding the rate from status before invoking ieee80211_rx_mesh_data(), so the RX_QUEUED arm consumes a value captured while status was still backed by valid memory.

CVSS v3
8.8
EG Score
8.8(high)
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
14%
KEV
Not listed

Published

July 19, 2026

Last Modified

July 20, 2026

Advisory Details (2)

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

wifi: mac80211: capture fast-RX rate before mesh reuses skb->cb - kernel/git/stable/linux.git - Linux kernel stable tree

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

wifi: mac80211: capture fast-RX rate before mesh reuses skb->cb - kernel/git/stable/linux.git - Linux kernel stable tree

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

Vendor Advisories for CVE-2026-64117(2)

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

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-oracle-7.0 (7.0.0-1008.8) @ resolute2026-07-26ubuntu
ubuntulinux-tools-azure-fde-7.0 (7.0.0-1009.9) @ resolute2026-07-26ubuntu

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.

All Vendor Advisories

(2)

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 23× in last 7d / 29× 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.

  1. 2026-07-27 14:14 UTCEPSS rescore
  2. 2026-07-27 10:17 UTCGHSA enrichment
  3. 2026-07-26 22:35 UTCEG score recompute
  4. 2026-07-26 22:35 UTCGHSA enrichment
  5. 2026-07-26 14:54 UTCEPSS rescore
  6. 2026-07-26 14:54 UTCEPSS rescore
  7. 2026-07-26 10:53 UTCEG score recompute
  8. 2026-07-26 10:53 UTCVendor advisory
  9. 2026-07-26 10:52 UTCGHSA enrichment
  10. 2026-07-25 14:18 UTCEPSS rescore
  11. 2026-07-25 14:18 UTCEPSS rescore
  12. 2026-07-24 14:18 UTCEPSS rescore
  13. 2026-07-24 14:18 UTCEPSS rescore
  14. 2026-07-23 14:18 UTCEPSS rescore
  15. 2026-07-23 14:18 UTCEPSS rescore
  16. 2026-07-23 03:22 UTCEG score recompute
  17. 2026-07-22 14:08 UTCEPSS rescore
  18. 2026-07-22 14:08 UTCEPSS rescore
  19. 2026-07-21 15:25 UTCEPSS rescore
  20. 2026-07-21 15:25 UTCEPSS rescore
  21. 2026-07-20 17:22 UTCEG score recompute
  22. 2026-07-20 17:21 UTCGHSA enrichment
  23. 2026-07-20 17:08 UTCEPSS rescore
  24. 2026-07-20 14:34 UTCEG score recompute 8.80
  25. 2026-07-20 14:34 UTCGHSA enrichment
Show 4 more
  1. 2026-07-20 14:32 UTCMITRE cvelistV5CVSS v3 → 8.8 · severity → HIGH
  2. 2026-07-19 17:49 UTCNVD update
  3. 2026-07-19 16:08 UTCEG score recompute
  4. 2026-07-19 16:03 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-64117?
CVE-2026-64117 is a high vulnerability published on July 19, 2026. In the Linux kernel, the following vulnerability has been resolved: wifi: mac80211: capture fast-RX rate before mesh reuses skb->cb ieee80211invokefast_rx() reads RX status through IEEE80211SKBRXCB(skb), which aliases the same skb->cb storage that ieee80211rxmeshdata() reuses as IEEE80211TX_INFO.…
When was CVE-2026-64117 disclosed?
CVE-2026-64117 was first published in the National Vulnerability Database on July 19, 2026, with the most recent update on July 20, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-64117 actively exploited?
CVE-2026-64117 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.5% of all scored CVEs.
What is the CVSS score of CVE-2026-64117?
CVE-2026-64117 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-64117?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64117, 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

Explore the affected products and dependency analysis for CVE-2026-64117

Explore →

Is Your Infrastructure Affected by CVE-2026-64117?

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