CVE-2026-64117

HIGHPre-NVD 8.88.8—
EchelonGraph scoreMEDIUM 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 — Patch released 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(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
14%
KEV
Not listed

Published

July 19, 2026

Last Modified

August 18, 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(3)

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

Patch Availability(7)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1016.16) @ resolute2026-09-11ubuntu
ubuntulinux-tools-nvidia-hwe-26.04 (7.0.0-2016.16) @ resolute2026-09-11ubuntu
ubuntulinux-tools-azure-fde-7.0 (7.0.0-1009.9) @ resolute2026-09-11ubuntu
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1015.15) @ resolute2026-09-11ubuntu
ubuntulinux-tools-gcp-edge (7.0.0-1011.11~24.04.1) @ noble2026-09-11ubuntu
ubuntulinux-tools-oracle-7.0 (7.0.0-1008.8) @ resolute2026-09-11ubuntu
redhatkernel-0:6.12.0-211.53.1.el10_22026-09-08redhat

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

(2 across 2 ecosystems)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (174 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (141 versions)7.0.12-1—

Weakness Classification(1)

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

Additional Vendor Advisories

(6)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 20× in last 7d / 122× 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 243 total refreshes for this CVE.

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

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 August 18, 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.7% 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

See which npm, PyPI, Go, and Maven packages are affected by 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.

Start Free Scan →Browse All CVEs