CVE-2026-64117
Last modified
CVE-2026-64117 is a high-severity vulnerability rated 8.8/10 on the CVSS scale. 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. EPSS estimates a 0.23% chance of exploitation in the next 30 days.
Description
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.
Metrics
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= 3468e1e0c639032a603450f0830ccabfa76f5806, < 2fb64f94f9afb774f2fa0c7835727d7a67f89f07; >= 3468e1e0c639032a603450f0830ccabfa76f5806, < d71c841be5d9e586ee7f36c0dc8ed4db0d9a1349 |
| Linux | Linux | 6.4 |
References
Timeline
- Published
- Last Modified
- Status
- Awaiting Analysis
Frequently Asked Questions
What is CVE-2026-64117?
How severe is CVE-2026-64117?
How do I fix CVE-2026-64117?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-64111In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2026-64112In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-64113In the Linux kernel, the following vulnerability has been re…9.8
- CVE-2026-64114In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-64115In the Linux kernel, the following vulnerability has been re…8.8
- CVE-2026-64116In the Linux kernel, the following vulnerability has been re…7.5
- CVE-2026-64118In the Linux kernel, the following vulnerability has been re…8.4
- CVE-2026-64119In the Linux kernel, the following vulnerability has been re…
- CVE-2026-6412Certificate policy and RFC 8446 compliance concerns regardin…4.3
- CVE-2026-64120In the Linux kernel, the following vulnerability has been re…
- CVE-2026-64121In the Linux kernel, the following vulnerability has been re…
- CVE-2026-64122In the Linux kernel, the following vulnerability has been re…9.8
Are you affected by CVE-2026-64117?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
