wifi: mac80211: capture fast-RX rate before mesh reuses skb->cb
CVE-2026-64117 · published 19 Jul 2026
How serious is it
- Severity: high, CVSS score 8.8 out of 10.
- No exploit prediction (EPSS) score yet.
- Not on the CISA list of exploited vulnerabilities.
- No public exploit in Exploit-DB.
Is your app affected by CVE-2026-64117?
Paste this prompt into Claude Code, Cursor or any AI coding tool: it runs a free Shippable scan of your project and fixes what it finds. Built with Lovable, Bolt or v0? Scan your live app. Or upload your package file.
Who is affected
- Linux Linux: 3468e1e0c639032a603450f0830ccabfa76f5806 to < 5fe97797412aa8bc0184f78379fafb594bcb7f66, 3468e1e0c639032a603450f0830ccabfa76f5806 to < 0cd37e746e98ab0baa6d8b812955220775b080d6, 3468e1e0c639032a603450f0830ccabfa76f5806 to < a2650f8461cd8ba287fee2992b36abe733c2bd5e, 3468e1e0c639032a603450f0830ccabfa76f5806 to < 2fb64f94f9afb774f2fa0c7835727d7a67f89f07
- Linux Linux: 6.4
How to check
- Find out whether you run the affected product and which version, then compare it with the versions above.
How to fix
Copies a prompt for Claude Code, Cursor or Codex that asks it to check whether you run this product.
- Apply the vendor's update or mitigation from the references below. If there is none yet, limit exposure of the affected service until there is.
- If a vulnerable version was live, check your logs and rotate the secrets that server could read.
The advisory
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.
Check your whole app
Dependencies are only half of it. Free and read-only: before you push, run npx shippable-dev scan localhost:3000 in your project folder, no account needed. For your live app, you prove it's yours with a one-line tag first.
References
- git.kernel.org/stable/c/5fe97797412aa8bc0184f78379fafb594bcb7f66
- git.kernel.org/stable/c/0cd37e746e98ab0baa6d8b812955220775b080d6
- git.kernel.org/stable/c/a2650f8461cd8ba287fee2992b36abe733c2bd5e
- git.kernel.org/stable/c/2fb64f94f9afb774f2fa0c7835727d7a67f89f07
- git.kernel.org/stable/c/d71c841be5d9e586ee7f36c0dc8ed4db0d9a1349
Merged from CVE List. Last updated 25 Oct 2026. All vulnerabilities · RSS · JSON