TOCTOU race in Linux kernel net/packet tpacket_snd() mmap'd vnet_hdr handling
CVE-2026-31700 is a local Linux kernel vulnerability in the net/packet subsystem, specifically the AF_PACKET TPACKET transmit path in tpacket_snd() when PACKET_VNET_HDR is enabled. In the vulnerable path, vnet_hdr points directly into the mmap'd TX ring buffer shared with userspace. The kernel first validates the virtio network header via __packet_snd_vnet_parse(), but later re-reads the header fields in virtio_net_hdr_to_skb() from the same user-controlled shared memory. Because the header is not copied to stable kernel memory before both operations, a concurrent userspace thread can modify vnet_hdr fields after validation but before use, creating a time-of-check to time-of-use race that bypasses the intended safety checks. The upstream fix copies vnet_hdr from the mmap'd ring buffer into a stack-local variable before validation and use, matching the already-safe behavior in packet_snd() and other kernel consumers such as tun.c, tap.c, and virtio_net.c.
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
8 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
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.