Skip to content
Noroxi
CVE-2026-98306· CVE.org (no NVD analysis yet)· CNA Linux

seg6: set IPSKB_L3SLAVE from IP6SKB_L3SLAVE on IPIP decapsulation

Noroxi assessment

Priority: Monitor (action score 0/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.18% (FIRST EPSS).
  • Fixed version: Linux Linux 1d9f5c78903dd25a3556229eb716dd465c5f3573, 5130afa025c95faa621adf8bac525baeb2b290d2, 72f410616000d21a0a6ec6c93a60301b9c92e95c; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 6.6.158.1-1.

Low priority for now. Upgrade to Linux Linux 1d9f5c78903dd25a3556229eb716dd465c5f3573, 5130afa025c95faa621adf8bac525baeb2b290d2, 72f410616000d21a0a6ec6c93a60301b9c92e95c; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 6.6.158.1-1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

—No exploit Fix available
Published
Oct 6, 2026
Updated
Oct 19, 2026
EPSS
0.1% · 7th percentile
CWE
—

Report tools

JSON

Action score

0

Monitor

Low priority for now.

CVSS
0 / 40 · —
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-98306

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 4.14affected
    • 891ef8dd2a8d14e4e73a81dcdb135b574c57f556 and later · before 1d9f5c78903dd25a3556229eb716dd465c5f3573affected · git
    • 891ef8dd2a8d14e4e73a81dcdb135b574c57f556 and later · before 72f410616000d21a0a6ec6c93a60301b9c92e95caffected · git
    • 891ef8dd2a8d14e4e73a81dcdb135b574c57f556 and later · before e4d7c52f15f572608374947c6c802052e1a2fc82affected · git
    • 891ef8dd2a8d14e4e73a81dcdb135b574c57f556 and later · before 5130afa025c95faa621adf8bac525baeb2b290d2affected · git
    • 891ef8dd2a8d14e4e73a81dcdb135b574c57f556 and later · before f8fb4738ccef5f9d107845b05734a56352747b1aaffected · git
    • 891ef8dd2a8d14e4e73a81dcdb135b574c57f556 and later · before ddf60220c925b54a1714c4722fdbdb12833232d0affected · git
    • 891ef8dd2a8d14e4e73a81dcdb135b574c57f556 and later · before 8c16e1ccc082a3763dfc6bc2d3f658c1a6336f9daffected · git
    • 891ef8dd2a8d14e4e73a81dcdb135b574c57f556 and later · before 7616242a2b37883f7322aaa1d2bd6cd0fed28315affected · git
    • before 4.14not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.190-16.1.190-1
Debian:12linux-6.12before 6.12.113-1~deb12u16.12.113-1~deb12u1
Debian:13linuxbefore 6.12.113-16.12.113-1
Debian:14linuxbefore 7.2.8-17.2.8-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2026-98304Oct 6, 2026 · net: bcmgenet: restore the hardware filters on open
    0Monitor
  • ← EarlierCVE-2026-98305Oct 6, 2026 · net: dsa: mxl862xx: disable the stats poll on teardown
    31Monitor
  • Later →CVE-2026-98307Oct 6, 2026 · wifi: ath11k: cleanup arsta in ath11k_mac_peer_cleanup_all()
    0Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux1d9f5c78903dd25a3556229eb716dd465c5f3573Vendor (CNA)
Linux Linux5130afa025c95faa621adf8bac525baeb2b290d2Vendor (CNA)
Linux Linux72f410616000d21a0a6ec6c93a60301b9c92e95cVendor (CNA)
Linux Linux7616242a2b37883f7322aaa1d2bd6cd0fed28315Vendor (CNA)
Linux Linux8c16e1ccc082a3763dfc6bc2d3f658c1a6336f9dVendor (CNA)
Linux Linuxddf60220c925b54a1714c4722fdbdb12833232d0Vendor (CNA)
Linux Linuxe4d7c52f15f572608374947c6c802052e1a2fc82Vendor (CNA)
Linux Linuxf8fb4738ccef5f9d107845b05734a56352747b1aVendor (CNA)
azl3 kernel 6.6.157.1-1 on Azure Linux 3.06.6.158.1-1 · Release NotesMicrosoft (MSRC)
debian:linux6.1.190-1 · Debian:12Package registry (OSV)
debian:linux6.12.113-1 · Debian:13Package registry (OSV)
debian:linux7.2.8-1 · Debian:14Package registry (OSV)
debian:linux-6.126.12.113-1~deb12u1 · Debian:12Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

  1. Published
  2. Fix recordedsame day
  3. TodayOct 24, 2026+18 d
EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

No CVSS vector for this record, so attack conditions can't be derived.

Weakness class (CWE)

—

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Exploit maturity— → none
  2. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (7 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records