Loading vulnerability…
CVE-2025-21790 is an unchecked-return-value vulnerability in the Linux kernel VXLAN implementation. The VXLAN initialization routine did not validate whether vxlan_vnigroup_init() succeeded. A failed initialization could leave VXLAN group state improperly initialized, after which VXLAN device cleanup invoked vxlan_vnigroup_uninit() on that state. This can produce a kernel null-pointer dereference and general-protection fault during device uninitialization.
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.
4 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Linux kernel VXLAN initialization return-value validation flaw.
A Linux kernel VXLAN flaw caused by failure to validate vxlan_vnigroup_init() success, which can lead to a kernel crash (availability impact).
Linux kernel VXLAN return-value handling flaw.
A Linux kernel VXLAN initialization error-handling flaw: vxlan_init() did not check whether vxlan_vnigroup_init() succeeded, which could later cause a null-pointer dereference/general-protection-fault crash during VXLAN cleanup or device registration failure handling.
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.