CVE-2026-64117
- Source
- https://cve.org/CVERecord?id=CVE-2026-64117
- Import Source
- https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-64117.json
- JSON Data
- https://api.osv.dev/v1/vulns/CVE-2026-64117
- Downstream
- Published
- 2026-07-19T15:40:16.941Z
- Modified
- 2026-07-21T03:47:56.923820805Z
- Severity
-
- 8.8 (High) CVSS_V3 - CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H CVSS Calculator
- Summary
- wifi: mac80211: capture fast-RX rate before mesh reuses skb->cb
- Details
-
In the Linux kernel, the following vulnerability has been resolved:
wifi: mac80211: capture fast-RX rate before mesh reuses skb->cb
ieee80211invokefastrx() reads RX status through IEEE80211SKBRXCB(skb), which aliases the same skb->cb storage that ieee80211rxmeshdata() reuses as IEEE80211TXINFO. 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 kfreeskb()'s it (no-route) before returning RXQUEUED. The caller's RXQUEUED arm then calls stastatsencoderate(status) on memory that is either zeroed (success path) or freed (no-route path). The latter is KASAN slab-use-after-free in ieee80211prepareandrxhandle.
Fix by encoding the rate from status before invoking ieee80211rxmeshdata(), so the RXQUEUED arm consumes a value captured while status was still backed by valid memory.
- Database specific
{ "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/64xxx/CVE-2026-64117.json", "cna_assigner": "Linux" }- References
-
- https://git.kernel.org/stable/c/2fb64f94f9afb774f2fa0c7835727d7a67f89f07
- https://git.kernel.org/stable/c/d71c841be5d9e586ee7f36c0dc8ed4db0d9a1349
- https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/64xxx/CVE-2026-64117.json
- https://nvd.nist.gov/vuln/detail/CVE-2026-64117
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git