Not ratedCVE-2026-80906

    Linux Kernel: security vulnerability (CVE-2026-80906)

    Published Last modified Sources: Ubuntu, HKCERT, Debian LTS, BSI, CVE.org, Msrc Update Guide, EUVD

    Share

    What is affected, what to do

    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.

    Update Linux Kernel to version 5.10.266, Linux Kernel to version 5.15.217, Linux Kernel to version 5.5.

    Affected
    • Linux Kernel lt 5.10.163..5.10.266
    • Linux Kernel lt 5.15.87..5.15.217
    • Linux Kernel lt 5.4.229..5.5
    • Linux Kernel lt 5.19..6.1.184
    • Linux Kernel lt 6.2..6.6.153
    • Linux Kernel lt 6.7..6.12.105
    • Linux Kernel lt 6.13..6.18.46
    • Linux Kernel lt 6.19..7.1.10
    Fixed in
    • Linux Kernel 5.10.266
    • Linux Kernel 5.15.217
    • Linux Kernel 5.5
    • Linux Kernel 6.1.184
    • Linux Kernel 6.6.153
    • Linux Kernel 6.12.105
    • Linux Kernel 6.18.46
    • Linux Kernel 7.1.10
    • Linux Kernel 7.2

    Not sure whether and how you are affected? Ask a question about this vulnerability

    Metrics

    —

    XIEM Effective CVSS

    No value is available for this vulnerability.

    0.0

    CVSS v3

    Severity Not rated on the scale from 0 to 10.

    Source: Ubuntu, HKCERT, Debian LTS, BSI, CVE.org, Msrc Update Guide, EUVD

    0.2 %

    EPSS score

    Low — model estimates < 1% exploitation likelihood.

    Source: FIRST EPSS, percentile 5.7

    Show all metrics
    Severity
    Not rated
    Priority (0–325)

    The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?

    Read in glossary
    24.13 Methodology
    Exploit maturity

    An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.

    Read in glossary
    no public PoC known
    CVSS v3

    CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.

    Read in glossary
    0.0
    EPSS score

    The EPSS score is the absolute model output for an individual vulnerability: the estimated probability of real-world exploitation within the next 30 days, expressed as a value between 0 and 1 (i.e. 0 % to 100 %). A score of 0.42 means „the model estimates a 42 % chance of real-world exploitation within 30 days“.

    Read in glossary
    0.2 %
    Low — model estimates < 1% exploitation likelihood.
    EPSS percentile

    The EPSS percentile is the relative position of a vulnerability within all EPSS-scored CVEs, expressed as a value between 0 and 1. A percentile of 0.90 means „this CVE has a higher EPSS score than 90 % of all other scored CVEs“. Unlike the EPSS score, it is not a probability — but a positioning within a ranking.

    Read in glossary
    5.7
    Low — this CVE sits in the lower 10% of all CVEs scored today.
    KEV status

    The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.

    Read in glossary
    —
    Published
    CISA assessment (SSVC)
    Exploitation: none known · not automatable · Technical impact: partial
    Source: CISA Vulnrichment, as of 6 November 2026

    Detection rules

    No NEOSEC detection rule is available for this vulnerability yet.

    Classification under NIS2 and CRA

    Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.

    NIS2

    NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.

    Read in glossary
    Handle the vulnerability in regular vulnerability handling under Art. 21(2)(e) NIS2.
    CRA

    The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.

    Read in glossary
    From 11.12.2027, Annex I Part II CRA requires manufacturers of affected products with digital elements to handle vulnerabilities without delay and provide security updates.
    ISO/IEC 27001

    ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.

    Read in glossary
    Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.

    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.

    Source: Ubuntu Security Notices, HKCERT (CC BY 3.0 HK) · HKCERT rating: medium, Debian LTS Advisories, BSI WID Portal, BSI CSAF, cvelistv5, NVD (NIST), CVE.org (MITRE), Microsoft Security Update Guide, ENISA EUVD

    Affected products

    The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.

    Affected products
    Affected versionsFixed in
    LinuxLinux
    • 5.15.87 – < 5.15.217
    • 5.19 – < 6.1.184
    • 6.2 – < 6.6.153
    • 6.19 – < 7.1.10
    • 6.7 – < 6.12.105
    • 5.4.229 – < 5.5
    • 5.10.163 – < 5.10.266
    • 6.13 – < 6.18.46
    • —
    • 5.15.217
    • 6.1.184
    • 6.6.153
    • 7.1.10
    • 6.12.105
    • 5.5
    • 5.10.266
    • 6.18.46
    • 7.2
    Red HatOpenShift
    • Container Platform
    • —

    Vendors and products

    Affected operating systems

    Affected operating systems
    Linuxdebianlinuxbookworm
    Linuxubuntulinuxjammy
    Linuxubuntulinuxnoble
    Linuxubuntulinuxresolute
    Linuxdebianlinux-6.12bookworm
    Linuxubuntulinux-awsjammy
    Linuxubuntulinux-awsnoble
    Linuxubuntulinux-awsresolute
    Linuxubuntulinux-aws-5.15focal
    Linuxubuntulinux-aws-6.8jammy
    Linuxubuntulinux-aws-7.0noble
    Linuxubuntulinux-aws-fipsjammy
    Linuxubuntulinux-aws-fipsnoble
    Linuxubuntulinux-azurejammy
    Linuxubuntulinux-azurenoble
    Linuxubuntulinux-azureresolute
    Linuxubuntulinux-azure-5.15focal
    Linuxubuntulinux-azure-6.8jammy
    Linuxubuntulinux-azure-fdenoble
    Linuxubuntulinux-azure-fderesolute
    Linuxubuntulinux-azure-fde-5.15focal
    Linuxubuntulinux-azure-fde-6.8jammy
    Linuxubuntulinux-azure-fde-7.0noble
    Linuxubuntulinux-azure-fipsjammy

    References & sources

    Changes to this CVE

    Who changed this CVE and when: NVD (analysis, affected products, CVSS), the CVE publisher (CNA) and additional providers such as CISA (ADP).

    1. Record modifiedCISA ADP

      CISA assessment (SSVC): exploitation: none known, automatable: no

      Show the original change
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      SSVC assessmentadded
      —
      {"id":"CVE-2026-80906","role":"CISA Coordinator","options":[{"exploitation":"none"},{"automatable":"no"},{"technicalImpact":"partial"}],"version":"2.0.3","timestamp":"2026-11-06T17:05:05.089294Z"}

      Source identifier: 134c704f-9b21-4f2e-91b3-4a467353bcc0

    2. ReceivedLinux

      Description added or changed

      Show 10 original changes
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      Descriptionadded
      —
      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 versions (publisher)added
      —
      New affected value received. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/80xxx/CVE-2026-80906.json">CVE-2026-80906</a>
      Referenceadded
      —
      https://git.kernel.org/stable/c/01fdecc0480d916c799dbee584833a4a37e94d06
      Referenceadded
      —
      https://git.kernel.org/stable/c/5479eb9b355f44745d7ccfe112386bd4f96eceea
      Referenceadded
      —
      https://git.kernel.org/stable/c/6386a6ffa2efba2965ed8e4fa303582c0b76a215
      Referenceadded
      —
      https://git.kernel.org/stable/c/6971cf319263d6a1b4096f9248aca9e57d77a1eb
      Referenceadded
      —
      https://git.kernel.org/stable/c/a4b82de96d465ddb44bc931145c0fa80c4fe9c9c
      Referenceadded
      —
      https://git.kernel.org/stable/c/e451e20adb869a983a21dda158625f024142e61f
      Referenceadded
      —
      https://git.kernel.org/stable/c/f9297abbcaba760b7a7b9d63b839f607f738013e
      Referenceadded
      —
      https://git.kernel.org/stable/c/fa86bc52ea8ba981f74f851fd61e2a3d3bc0feac

      Source identifier: 416baaa9-dc9f-4396-8d5f-8c081fb06d67

    Embed badge

    Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.

    Badge preview for CVE-2026-80906
    <a href="https://intel.neosec.eu/en/cve/CVE-2026-80906"><img src="https://intel.neosec.eu/badge/cve/CVE-2026-80906.svg?lang=en" alt="CVE-2026-80906 – NEOSEC Intel" height="20"></a>