CVE-2026-80906

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

N/A
Published: September 4, 2026 at 05:19 PM UTC
Updated: September 4, 2026 at 06:36 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v ≥ 5.4.2295.10.163 ≤ v < 5.10.2665.15.87 ≤ v < 5.15.2175.19 ≤ v < 6.1.1845.19 ≤ v < 6.12.1055.19 ≤ v < 6.18.465.19 ≤ v < 6.6.1535.19 ≤ v < 7.1.105.19 ≤ v < 7.25.4.229 ≤ v < 5.55.10.1635.15.875.195.4.2299ff46c36df2e0a1ac352f2f4038eaf3f0f7361b8ad3f90a9c4a2c74bb3711f2031bffda4ec44c849c2137d565ceb505de69593c181a0543bc4083838dfed913e8b55a0c2c4906f1242fd38fd9a116e49
Vendor states this is fixed in 01fdecc0480d916c799dbee584833a4a37e94d06 (fixed)
Vendor states this is fixed in 5479eb9b355f44745d7ccfe112386bd4f96eceea (fixed)
Vendor states this is fixed in 6386a6ffa2efba2965ed8e4fa303582c0b76a215 (fixed)
Vendor states this is fixed in 6971cf319263d6a1b4096f9248aca9e57d77a1eb (fixed)
Vendor states this is fixed in a4b82de96d465ddb44bc931145c0fa80c4fe9c9c (fixed)
Vendor states this is fixed in e451e20adb869a983a21dda158625f024142e61f (fixed)
Vendor states this is fixed in f9297abbcaba760b7a7b9d63b839f607f738013e (fixed)
Vendor states this is fixed in fa86bc52ea8ba981f74f851fd61e2a3d3bc0feac (fixed)
Vendor states this is fixed in 5.10.266 (unaffected)
Vendor states this is fixed in 5.15.217 (unaffected)
Vendor states this is fixed in 5.19 (unaffected)
Affected range stops below 5.5, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 6.1.184 (unaffected)
Vendor states this is fixed in 6.12.105 (unaffected)
Vendor states this is fixed in 6.18.46 (unaffected)
Vendor states this is fixed in 6.6.153 (unaffected)
Vendor states this is fixed in 7.1.10 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card