CVE-2026-98096

What it is

In the Linux kernel, the following vulnerability has been resolved: ipv6: sr: restore network header before routing and forwarding ipv6_srh_rcv() runs with skb->data at the Segment Routing Header (SRH) while skb_network_header() points at the IPv6 header. When segments_left > 0, ipv6_srh_rcv() previously restored the skb->data position by pushing sizeof(struct ipv6hdr), assuming the SRH immediately followed the fixed IPv6 header. If another extension header (such as a Hop-by-Hop options header) precedes the SRH, skb_network_offset() remained negative. This led to two problems: 1. During ip6_route_input(), fib6_rules_early_flow_dissect() invokes __skb_flow_dissect() which passes the negative skb_network_offset() to flow dissection, breaking BPF and C flow dissector logic. 2. If forwarded via ip6_forward() or redirected via act_mirred, downstream handlers (like sch_fragment() or neighbour output) pass the negative offset as an unsigned length, triggering OOB memcpy or buffer overflows. Fix this by pushing -skb_network_offset(skb) before routing, ensuring skb_network_offset(skb) is 0 for route lookup / flow dissection as well as downstream forwarding. On the loopback path, pull skb_transport_offset(skb) to restore skb->data to the SRH before looping back.

At a glance

Exploitability

Can be exploited over the network without logging in. High risk of data tampering, service disruption.

Exploit odds

0.5% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2026-09-25 10:19 UTC ReservedThe CVE id was reserved by its CNA
2. 2026-09-25 11:17 UTC PublishedDisclosed publicly on CVE.org and NVD
3. 2026-10-28 18:58 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 0.5% in the next 30 days (EPSS).
• Severity: 7.4 HIGH (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2026-09-25 11:17 UTC

Last modified

2026-10-28 18:58 UTC

Exploit probability

0.5% · EPSS, next 30 days

Weakness

CWE-787 · Out-of-bounds write

Record status

Analyzed

Affected

• Linux Kernel < 5.10.271
• Linux Kernel < 5.15.222
• Linux Kernel < 6.1.189
• Linux Kernel < 6.6.158
• Linux Kernel < 6.12.111
• Linux Kernel < 6.18.53
• Linux Kernel < 7.2.7
• Linux Kernel 7.3

Attack profile CVSS 3.1 · 7.4

Attack vector

Network

Complexity

High

Privileges needed

None

User interaction

None

Scope

Unchanged

Confidentiality

None

Integrity

High

Availability

High

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2026-98096.md and follow it. Check whether this project is affected by CVE-2026-98096. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge