Loading vulnerability…
A double free vulnerability exists in the Linux kernel's mac80211 subsystem when handling mesh network join and leave operations. Specifically, after commit 6a01afcf8468, the mesh Information Element (IE) memory is freed both during mesh leave (ieee80211_leave_mesh) and again during mesh join (copy_mesh_setup), leading to potential memory corruption or kernel panics. This is triggered when mesh join/leave operations are performed in quick succession, particularly when not using wpa_supplicant, but rather custom tools like Senf that interact directly with nl80211.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
5 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A Linux kernel mac80211 double-free vulnerability triggered during mesh-network join operations.
A Linux kernel mac80211 mesh networking double-free vulnerability. A mesh leave followed by a mesh rejoin can free mesh IE data twice, potentially causing memory corruption or a kernel panic. It was observed with an encrypted mesh when an application such as Senf directly uses nl80211 calls.
A Linux kernel mac80211 potential double-free vulnerability during mesh join operations.
A potential double-free vulnerability in the Linux kernel mac80211 subsystem during mesh-network joining.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.