← All Advisories
Reported from OT-Advisories.com as of

CVE-2026-64568

Last refreshed2026-11-03

Status: UPDATED  |  Advisory ID: CVE-2026-64568

Key Details

CVECVE-2026-64568
CVSS Score / Version
7.8 (High) / CVSS v3.1
Updated2026-11-03
CVSS Vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CVSS Prose
attack vector is local; attack complexity is low; privileges required is low; user interaction is none; scope is unchanged; confidentiality impact is high; integrity impact is high; availability impact is high.
Affected products
Linux Kernel

Affected Products, Subsystems & Sectors

VendorProductAffected VersionsPatch Status
LinuxLinux Kernel
SubsystemsOT Supporting Infrastructure
SectorsAll Sectors

What to Know

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(). (NVD)

What to Do

Monitor Linux's web page for any future patch releases.

References

SourceReference
NVDhttps://nvd.nist.gov/vuln/detail/CVE-2026-64568
CVEhttps://www.cve.org/CVERecord?id=CVE-2026-64568
Report compilation © 2026 OT-Advisories.com  ·  CC BY 4.0  ·  Source materials remain the property of their respective publishers as cited.