Answer in brief
CVE-2026-64570 records a High severity (CVSS 7.8) vulnerability in wifi: mac80211: fix fils_discovery double free on alloc failure. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=3b1c256eb4aedfc71dd97d5951ccff824b41d628 <e2c55079155a953db669ca1986a985fa286bad95 || >=3b1c256eb4aedfc71dd97d5951ccff824b41d628 <5baaa1042f71dd4b8e418f2cdd516808702d229b || >=3b1c256eb4aedfc71dd97d5951ccff824b41d628 <1981fba71797ec95e6755fb882cad88899a2a84f || >=3b1c256eb4aedfc71dd97d5951ccff824b41d628 <286e52a799fa158bdbd77da1426c4d93f9a6e7ad | e2c55079155a953db669ca1986a985fa286bad95, 5baaa1042f71dd4b8e418f2cdd516808702d229b, 1981fba71797ec95e6755fb882cad88899a2a84f, 286e52a799fa158bdbd77da1426c4d93f9a6e7ad |
| Linux/Linuxgeneric | 6.7 | Not reported |
Published upstream
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 17, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
In the Linux kernel, the following vulnerability has been resolved: wifi: mac80211: fix fils_discovery double free on alloc failure ieee80211_set_fils_discovery() calls kfree_rcu() on the old template before allocating the replacement. If the kzalloc() then fails, it returns -ENOMEM while link->u.ap.fils_discovery still points at the object already queued for freeing. A later update or AP teardown (ieee80211_stop_ap()) re-queues that same rcu_head; the second free is caught by KASAN when the RCU sheaf is processed in softirq: BUG: KASAN: double-free in rcu_free_sheaf (mm/slub.c:5850) Free of addr ffff88800c065280 by task swapper/0/0 ... __rcu_free_sheaf_prepare (mm/slub.c:2634 mm/slub.c:2940) rcu_free_sheaf (mm/slub.c:5850) rcu_core (kernel/rcu/tree.c:2617 kernel/rcu/tree.c:2869) handle_softirqs (kernel/softirq.c:622) The buggy address belongs to the cache kmalloc-96 of size 96 Queue the old object for kfree_rcu() only after the new one is published, matching ieee80211_set_probe_resp() and ieee80211_set_s1g_short_beacon().
Quoted source text, attributed separately from HOL analysis.