CVE-2026-80905

published 4 Sep 2026 · updated 17 Nov 2026

net: tap: fix wrong transport_header when sending VLAN-tagged frame

5.5MediumCVSS 5.5EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel f1d297cad5c1eacd9fadfd0346ad97405ffbf97c, Kernel 4.21, Kernel 5ffaa5d7f56ab24a8e23cf131eadfef31a3bbc4b and 9 more.

In the Linux kernel, the following vulnerability has been resolved: net: tap: fix wrong transport_header when sending VLAN-tagged frame In tap_get_user_xdp(), when processing a VLAN-tagged frame (e.g. ETH_P_8021Q), skb_set_network_header() is called first to advance network_header past the VLAN tag to the inner protocol header. skb_probe_transport_header() is then called with skb->protocol still set to ETH_P_8021Q, while nhoff (derived from skb_network_offset()) already points past the VLAN tag to the inner protocol header. In __skb_flow_dissect(), proto is initialized to ETH_P_8021Q and nhoff points past the VLAN tag. When the dissector hits case ETH_P_8021Q, it reads a struct vlan_hdr at the current nhoff via __skb_header_pointer(), but that offset contains the inner protocol header (e.g. an IP header). The bytes are misinterpreted as a VLAN header, yielding a garbage encapsulated EtherType that matches no known protocol. The dissector returns false, so skb_probe_transport_header() never calls skb_set_transport_header(), leaving transport_header at its uninitialized sentinel value (~0U). Move skb_set_network_header() to after skb_probe_transport_header(). At the time skb_probe_transport_header() is called, network_header still points to the VLAN header (offset ETH_HLEN), so nhoff is correct and the flow dissector can parse the VLAN header, extract the inner EtherType, and advance nhoff to the inner protocol header, allowing transport_header to be set correctly.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel>=8c76e77f9069f10505c08e02646c3ee11ad79038 <f1d297cad5c1eacd9fadfd0346ad97405ffbf97c, >=4.20.1 <4.21, >=8c76e77f9069f10505c08e02646c3ee11ad79038 <5ffaa5d7f56ab24a8e23cf131eadfef31a3bbc4b, >=8c76e77f9069f10505c08e02646c3ee11ad79038 <88b79ac89ecc04d7f2613f7e1c0b46f0c4ddb2f3, >=8c76e77f9069f10505c08e02646c3ee11ad79038 <a8f49e83e4447b885376e6a937d62df883cc8824, >=8c76e77f9069f10505c08e02646c3ee11ad79038 <c0376820922d255ae1d103c32345a6ec4c3266f7, >=8c76e77f9069f10505c08e02646c3ee11ad79038 <cbb35cbe8db268fefe34c23df15348cf99025298, =3cae5ef1f37a475faf7c40bc6a3c170779f3e0b1, =5.0f1d297cad5c1eacd9fadfd0346ad97405ffbf97c, 4.21, 5ffaa5d7f56ab24a8e23cf131eadfef31a3bbc4b, 88b79ac89ecc04d7f2613f7e1c0b46f0c4ddb2f3, a8f49e83e4447b885376e6a937d62df883cc8824, c0376820922d255ae1d103c32345a6ec4c3266f7, cbb35cbe8db268fefe34c23df15348cf99025298
linux-kernel: Kernel>=5.0.0 <6.1.191, >=6.13.0 <6.18.46, >=6.19.0 <7.1.10, >=6.2.0 <6.6.160, >=6.7.0 <6.12.114, >=4.20.1 <4.216.1.191, 6.18.46, 7.1.10, 6.6.160, 6.12.114, 4.21

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-80905 severity on Zeptric[![CVE-2026-80905](https://zeptric.io/badge/cve/CVE-2026-80905.svg)](https://zeptric.io/cve/CVE-2026-80905)