CVE-2026-80906: Linux kernel · net: packet: fix wrong transport_header when sending VLAN-tagged frame
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in fa86bc52ea8ba981f74f851fd61e2a3d3bc0feac : update Linux kernel when convenient.
Data as of 6 Nov 2026, 17:33 UTC
Rated Medium by Threat Radar's AI analysis · CVSS not yet scored by NVD
Thin evidence
One scorer or none- CISA SSVC
- Exploitation
- No evidence of active exploitation and no public proof of concept
- Automatable
- Attackers cannot reliably automate steps 1–4 of the kill chain
- Technical impact
- Limited control over the software or limited information exposure
CISA SSVC assessment, 2026-11-06.
- Patch
- Available – fixed in fa86bc52ea8ba981f74f851fd61e2a3d3bc0feac, f9297abbcaba760b7a7b9d63b839f607f738013e, e451e20adb869a983a21dda158625f024142e61f +8
Exploitation evidence
Disclosed: evidence found.
CVE published 4 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 6 Nov 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
AI-suggested
The vulnerability has been fixed in Linux kernel versions 5.10.266, 5.15.217, 5.5, and later. Users and administrators should upgrade to these or later versions to remediate the issue. No additional mitigation steps are indicated.
Description
A vulnerability in the Linux kernel's packet handling code causes incorrect setting of the transport header when sending VLAN-tagged frames. This occurs due to improper parsing of VLAN headers, leading to the transport_header field being left uninitialized. The issue has been fixed by reordering function calls to correctly parse VLAN headers and set the transport header.
References
- git.kernel.org/stable/c/a4b82de96d465ddb44bc931145c0fa80c4fe9c9c (opens in a new tab)
- git.kernel.org/stable/c/fa86bc52ea8ba981f74f851fd61e2a3d3bc0feac (opens in a new tab)
- git.kernel.org/stable/c/5479eb9b355f44745d7ccfe112386bd4f96eceea (opens in a new tab)
- git.kernel.org/stable/c/e451e20adb869a983a21dda158625f024142e61f (opens in a new tab)
- git.kernel.org/stable/c/6971cf319263d6a1b4096f9248aca9e57d77a1eb (opens in a new tab)
- git.kernel.org/stable/c/f9297abbcaba760b7a7b9d63b839f607f738013e (opens in a new tab)
- git.kernel.org/stable/c/6386a6ffa2efba2965ed8e4fa303582c0b76a215 (opens in a new tab)
- git.kernel.org/stable/c/01fdecc0480d916c799dbee584833a4a37e94d06 (opens in a new tab)