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-98306seg6: set IPSKB_L3SLAVE from IP6SKB_L3SLAVE on IPIP decapsulation

Description

In the Linux kernel, the following vulnerability has been resolved: seg6: set IPSKB_L3SLAVE from IP6SKB_L3SLAVE on IPIP decapsulation When an SRv6 packet arrives on an interface enslaved to a VRF, vrf_ip6_rcv() sets IP6SKB_L3SLAVE in IP6CB, but decap_and_validate() has never set IPSKB_L3SLAVE in IPCB. The bit stayed clear in the common case, and with CONFIG_IPV6_MIP6 the leftover frag_max_size of a reassembled outer packet could even set it, with no VRF involved. Commit 44930446dde4 ("ipv6: seg6: clear IPv4 control block on IPIP decapsulation") then made the unreliable bit reliably clear. The effect of the missing flag is visible with End.DX4 when a delivery to a local address of the node reaches the socket lookup. For example, a UDP socket bound to the enslaved ingress interface does not receive any of the decapsulated packets, while an unbound socket outside the VRF does. This contradicts Documentation/networking/vrf.rst: by default the scope of an unbound UDP or TCP socket is limited to the default VRF. Set IPSKB_L3SLAVE for IPv4 in decap_and_validate(), which already does the same for IPv6. The socket lookup then matches the decapsulated packet like any other packet received on that enslaved interface. Such a packet matches an unbound UDP or TCP socket only when udp_l3mdev_accept or tcp_l3mdev_accept is set.

Timeline

  1. ID reserved

    By Linux

  2. · 11 days later

    Published

  3. · 13 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

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.18% · top 92% of all CVEs (14 Nov 2026)
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected 891ef8dd2a8d14e4e73a81dcdb135b574c57f556 – < 1d9f5c78903dd25a3556229eb716dd465c5f3573
    • affected 891ef8dd2a8d14e4e73a81dcdb135b574c57f556 – < 72f410616000d21a0a6ec6c93a60301b9c92e95c
    • affected 891ef8dd2a8d14e4e73a81dcdb135b574c57f556 – < e4d7c52f15f572608374947c6c802052e1a2fc82
    • affected 891ef8dd2a8d14e4e73a81dcdb135b574c57f556 – < 5130afa025c95faa621adf8bac525baeb2b290d2
    • affected 891ef8dd2a8d14e4e73a81dcdb135b574c57f556 – < f8fb4738ccef5f9d107845b05734a56352747b1a
    • affected 891ef8dd2a8d14e4e73a81dcdb135b574c57f556 – < ddf60220c925b54a1714c4722fdbdb12833232d0
    • affected 891ef8dd2a8d14e4e73a81dcdb135b574c57f556 – < 8c16e1ccc082a3763dfc6bc2d3f658c1a6336f9d
    • affected 891ef8dd2a8d14e4e73a81dcdb135b574c57f556 – < 7616242a2b37883f7322aaa1d2bd6cd0fed28315
  • Linux · Linux

    • affected 4.14
    • unaffected < 4.14
    • unaffected 5.10.271 – ≤ 5.10.*
    • unaffected 5.15.222 – ≤ 5.15.*
    • unaffected 6.1.189 – ≤ 6.1.*
    • unaffected 6.6.158 – ≤ 6.6.*
    • unaffected 6.12.112 – ≤ 6.12.*
    • unaffected 6.18.54 – ≤ 6.18.*
    • unaffected 7.2.8 – ≤ 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-98306 badge
[![CVE-2026-98306](https://cveledger.app/badge/CVE-2026-98306.svg)](https://cveledger.app/cve/CVE-2026-98306)

Record last updated .