Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-80976

seg6: reset IP6CB after IPv6 decapsulation

Description

In the Linux kernel, the following vulnerability has been resolved: seg6: reset IP6CB after IPv6 decapsulation decap_and_validate() pulls the outer SRv6 headers and makes the inner packet the skb network header. The IPv6 control block still contains values collected while parsing the outer packet, including nhoff and extension-header flags. End.DX6 and End.DT6 route the inner IPv6 packet directly to the IPv6 input path. An unprivileged user can reach End.DT6 from a user and net namespace by installing a local SID and injecting an outer packet with Hop-by-Hop and Destination Options headers followed by an SRH and a minimal inner IPv6 packet. The outer extension headers leave a large nhoff in IP6CB. After decapsulation, ip6_protocol_deliver_rcu() uses that stale offset on the inner packet and reads beyond the skb head. KASAN reports: BUG: KASAN: slab-out-of-bounds in ip6_protocol_deliver_rcu ip6_protocol_deliver_rcu+0x1118/0x1450 ip6_input_finish+0x11b/0x240 seg6_local_input_core+0xed/0x2e0 lwtunnel_input+0x1e9/0x4e0 ipv6_rthdr_rcv+0x525f/0x6c50 ip6_protocol_deliver_rcu+0xcb7/0x1450 Before clearing IP6CB for an inner IPv6 packet, save its incoming interface index and L3 slave state. Restore both after the clear and set nhoff to the inner IPv6 base-header nexthdr field. Use IP6CB(skb)->iif rather than skb->skb_iif because VRF processing can replace skb_iif with the L3 master while IP6CB keeps the receiving interface. Preserve IP6SKB_L3SLAVE for the same reason.

Timeline

  1. ID reserved

    By Linux

  2. · 16 days later

    Published

  3. · 38 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-80976, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1Critical9.8CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Received3.1Critical9.8CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.71% · top 46% of all CVEs (11 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Critical 9.8.

Affected products

  • Linux · Linux

    • affected d7a669dd2f8ba07a17423f4ad586dfc0379882f7 – < d1f0d353358987ca87f21d8956e2d2854951130d
    • affected d7a669dd2f8ba07a17423f4ad586dfc0379882f7 – < a0e2b0a3718f0cf9fb0ee41710b4a6348a7315c8
    • affected d7a669dd2f8ba07a17423f4ad586dfc0379882f7 – < 9ae92198c24d7dacd4070e2f34f6e1ed3a63061c
    • affected d7a669dd2f8ba07a17423f4ad586dfc0379882f7 – < 96c74420ac92930a7e0f21770818544eee4a93d7
    • affected d7a669dd2f8ba07a17423f4ad586dfc0379882f7 – < 2b154e96fcb3f01fd42765c64e0a56820fbc16eb
    • affected d7a669dd2f8ba07a17423f4ad586dfc0379882f7 – < cfa186a0857a0f831dfca67b16bbc40ecfdf3280
    • affected d7a669dd2f8ba07a17423f4ad586dfc0379882f7 – < c73fb911e02b9a766c950bc9707f3e3a96ffd702
    • affected d7a669dd2f8ba07a17423f4ad586dfc0379882f7 – < f967455fb2a5a2079b9eb5823e9ccf359174bf9f
  • Linux · Linux

    • affected 4.14
    • unaffected < 4.14
    • unaffected 5.10.270 – ≤ 5.10.*
    • unaffected 5.15.221 – ≤ 5.15.*
    • unaffected 6.1.188 – ≤ 6.1.*
    • unaffected 6.6.157 – ≤ 6.6.*
    • unaffected 6.12.109 – ≤ 6.12.*
    • unaffected 6.18.50 – ≤ 6.18.*
    • unaffected 7.2.4 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-80976 badge
[![CVE-2026-80976](https://cveledger.app/badge/CVE-2026-80976.svg)](https://cveledger.app/cve/CVE-2026-80976)

Record last updated .