CVE-2026-46322 is a Linux kernel memory-management flaw in the TUN networking path, specifically in tun_xdp_one(). When build_skb() fails after vhost_net_build_xdp() has allocated a page for the frame, the error path sets ret to -ENOMEM and exits without freeing the allocated page. Because tun_sendmsg() discards the per-buffer error and still returns total_len, vhost_tx_batch() follows the success path and does not release the page either. As a result, each build_skb() failure in a batch leaks one page-frag chunk. The fix adds the missing page release on the build_skb() failure path, consistent with the put_page() handling already present in other tun_xdp_one() error exits.
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.
3 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
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.