Loading vulnerability…
CVE-2024-27410 is an input-validation flaw in the Linux kernel Wi-Fi nl80211 subsystem. When an interface was not already operating in mesh mode, nl80211 permitted a request to change both the interface type to mesh and the mesh ID. Processing the mesh-ID update in this state overwrote data in the interface-type-specific wdev->u union belonging to the current interface type. Subsequent interface switching in cfg80211_change_iface() could then operate on corrupted or inappropriate union state. The upstream fix rejects interface-type changes when a mesh-ID change is requested in the same operation.
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.
8 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
An improper interface-type and mesh-ID change handling issue in Linux kernel nl80211.
A Linux kernel Wi-Fi nl80211 vulnerability related to interface-type changes accompanied by mesh-ID changes.
Linux kernel nl80211 interface-type and mesh-ID change validation vulnerability.
Linux kernel nl80211 interface-type and mesh-ID change validation flaw.
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.