Menu

Star on GitHub · 3.2k

CVE-2026-31700

7.8 · HIGH

In the Linux kernel, the following vulnerability has been resolved: net/packet: fix TOCTOU race on mmap'd vnet_hdr in tpacket_snd() In tpacket_snd(), when PACKET_VNET_HDR is enabled, vnet_hdr poi…

Published May 1, 2026CWE-362EPSS 0.11%

Overview

CVE-2026-31700 is a high-severity vulnerability. It was published on May 1, 2026 and has a CVSS 3.1 base score of 7.8 (HIGH).

This vulnerability has a CVSS 3.1 base score of 7.8, rated HIGH. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

Technical description

In the Linux kernel, the following vulnerability has been resolved:

net/packet: fix TOCTOU race on mmap'd vnet_hdr in tpacket_snd()

In tpacket_snd(), when PACKET_VNET_HDR is enabled, vnet_hdr points

directly into the mmap'd TX ring buffer shared with userspace. The

kernel validates the header via __packet_snd_vnet_parse() but then

re-reads all fields later in virtio_net_hdr_to_skb(). A concurrent

userspace thread can modify the vnet_hdr fields between validation

and use, bypassing all safety checks.

The non-TPACKET path (packet_snd()) already correctly copies vnet_hdr

to a stack-local variable. All other vnet_hdr consumers in the kernel

(tun.c, tap.c, virtio_net.c) also use stack copies. The TPACKET TX

path is the only caller of virtio_net_hdr_to_skb() that reads directly

from user-controlled shared memory.

Fix this by copying vnet_hdr from the mmap'd ring buffer to a

stack-local variable before validation and use, consistent with the

approach used in packet_snd() and all other cal

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2026-31700?

CVE-2026-31700 is a high-severity vulnerability. It was published on May 1, 2026 and has a CVSS 3.1 base score of 7.8 (HIGH).

How severe is CVE-2026-31700?

This vulnerability has a CVSS 3.1 base score of 7.8, rated HIGH. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

How do I fix or remediate CVE-2026-31700?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2026-31700?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2026-31700 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related HIGH CVEs from 2026

View all