Loading vulnerability…
A flaw in the Linux kernel 8021q VLAN subsystem causes a reference count imbalance for VLAN ID 0 when the rx-vlan-filter feature is toggled while a network device is running. When VLAN filtering is enabled, the kernel may automatically add VLAN 0 on NETDEV_UP and remove it on NETDEV_DOWN. The vulnerable logic incorrectly bases deletion behavior on the current rx-vlan-filter state rather than on whether VLAN 0 was actually auto-added earlier. This can produce two failure modes: a memory leak when VLAN 0 is not removed after filtering is disabled at runtime, and an inconsistent refcount state in which VLAN 0 is deleted despite never having had its reference count incremented in the corresponding path. In the latter case, subsequent VLAN device teardown can trigger a NULL pointer dereference or kernel BUG in VLAN unregistration due to missing VLAN metadata after premature free. The fix records whether VLAN 0 was automatically added and uses that state to decide whether it should be removed during NETDEV_DOWN.
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.
11 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
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.