CVE-2026-64568

CVE CVE-2026-64568EUVD EUVD-2026-53262Published 2026-08-05T08:08:06.000ZLast changed 2026-08-08T15:13:09.000ZCVSS 7.8

What the advisory describes

In the Linux kernel, the following vulnerability has been resolved: wifi: mac80211: fix unsol_bcast_probe_resp double free on alloc failure ieee80211_set_unsol_bcast_probe_resp() calls kfree_rcu() on the old template before allocating the replacement. If the kzalloc() then fails, it returns -ENOMEM while link->u.ap.unsol_bcast_probe_resp still points at the object already queued for freeing. A later update or AP teardown 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 ffff88800d06f300 by task exploit/145 ... __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-128 of size 128 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().

Source: EUVD (ENISA), in the words of the advisory.

Products the advisory names

These come from the advisory itself, not from any check we performed.

Linux — Linux patch: 7.2-rc4; 3b1c256eb4aedfc71dd97d5951ccff824b41d628 <ca27a81cd77b698e5eb586a011bee6800c7ee4bd; patch: 7.1.6; patch: 6.12.101; 6.7; patch: 6.18.42; 3b1c256eb4aedfc71dd97d5951ccff824b41d628 <0ace76e410d7f7d813b605825a3e593a79c3958f; 3b1c256eb4aedfc71dd97d5951ccff824b41d628 <d62b55b7c7dc62887d7fd5648fb38f0bfaef53ae; patch: 0; 3b1c256eb4aedfc71dd97d5951ccff824b41d628 <1d067abcd37062426c59ec73dbc4e87a63f33fea

The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.

Carried in the product catalogue

An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.

Linux — Linux

Does this concern one of your customers?

This page cannot answer that — it does not know your estate. Whoever has recorded their environments gets the answer the morning after publication, together with a paragraph they can forward to the customer unedited.

Try it for 28 days

Patchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.