CVE-2026-64117

Analyzed Analyzed - Analysis Complete

Memory Corruption in Linux Kernel WiFi Subsystem

Publication date: 2026-07-19

Last updated on: 2026-08-18

Assigner: kernel.org

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-07-19

Last Modified

2026-08-18

Generated

2026-08-30

AI Q&A

2026-07-19

EPSS Evaluated

2026-08-28

NVD

CVE-2026-64117

EUVD

EUVD-2026-45802

Affected Vendors & Products

Vendor	Product	Version / Range
linux	linux_kernel	7.1
linux	linux_kernel	7.1
linux	linux_kernel	7.1
linux	linux_kernel	7.1
linux	linux_kernel	From 6.4 (inc) to 7.0.11 (exc)

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-416	The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer.

Attack-Flow Graph

Executive Summary

This vulnerability in the Linux kernel involves a memory corruption issue where the fast-RX rate is captured after mesh reuses skb->cb storage. The ieee80211_invoke_fast_rx() function reads RX status through IEEE80211_SKB_RXCB(skb), which shares the same memory location as IEEE80211_TX_INFO used by ieee80211_rx_mesh_data(). This leads to a use-after-free condition when the caller processes the skb after mesh operations, potentially causing a slab-use-after-free in ieee80211_prepare_and_rx_handle.

Detection Guidance

This vulnerability is specific to the Linux kernel's mac80211 subsystem and involves a use-after-free issue in the mesh forwarding path. Detection requires checking kernel logs for slab-use-after-free errors related to ieee80211_prepare_and_rx_handle or sta_stats_encode_rate. Use commands like dmesg | grep -i 'slab-use-after-free\|ieee80211_prepare_and_rx_handle\|sta_stats_encode_rate' to search for relevant errors.

Impact Analysis

This vulnerability could allow an attacker to cause a denial-of-service (DoS) condition by triggering a kernel crash or memory corruption. Systems running affected versions of the Linux kernel with WiFi functionality enabled may be vulnerable to remote attacks via WiFi networks.

Compliance Impact

This vulnerability is a memory corruption issue in the Linux kernel's WiFi subsystem that could lead to a use-after-free condition. It does not directly impact compliance with standards like GDPR or HIPAA, as those focus on data protection and privacy rather than kernel memory management. However, if exploited, it could potentially lead to system instability or crashes, indirectly affecting availability aspects of compliance requirements.

Mitigation Strategies

Apply the latest kernel security updates from your Linux distribution to patch the mac80211 subsystem. If immediate patching is not possible, disable mesh networking features if they are not required. Monitor kernel logs for signs of exploitation or crashes.

Hi! I’m here to help you understand CVE-2026-64117. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70