Linux kernel tap_get_user_xdp() page-frag memory leak
CVE-2026-46320 is a Linux kernel memory management flaw in the TAP/XDP transmit path, specifically in tap_get_user_xdp(). The function can reject frames shorter than ETH_HLEN with -EINVAL and can also fail with -ENOMEM when build_skb() returns an error. In the vulnerable implementation, both error paths jump to a common err label without freeing the page previously allocated by vhost_net_build_xdp() for the frame. Because tap_sendmsg() ignores the per-buffer return value and always returns 0, vhost_tx_batch() follows the success path and does not release the page either. As a result, each rejected frame in a batch leaks one page-frag chunk. The fix is to free the allocated page on both affected error paths before skb construction. This issue is described as the TAP-side counterpart of a similar leak previously identified in tun_xdp_one().
Are you exposed to this one?
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.
Impact, mitigation & remediation
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Mitigation
If you can’t patch tonight, do this now.
Remediation
Patch, then assume compromise.
Exploits
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Affected products & vendors
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.
Recent activity
14 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.
The version that knows your environment.
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.