CVE-2026-98096

CVE CVE-2026-98096EUVD EUVD-2026-86926Published 2026-09-25T10:24:27.000ZLast changed 2026-09-25T14:42:04.000ZCVSS 7.4

What the advisory describes

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.

Source: EUVD (ENISA), in the words of the advisory.

Products the advisory names

These come from the advisory itself, not from any check we performed.

Linux — Linux 4.10; patch: 0; patch: 7.2.7; patch: 6.18.53; patch: 7.3-rc2; 1ababeba4a21f3dba3da3523c670b207fb2feb62 <975b5b067f525a1b1338c4a3bee1c46545801518; 1ababeba4a21f3dba3da3523c670b207fb2feb62 <ce4c8beedc19aceeab0e7bdc6f34394fb158c47c; patch: 6.12.111; 1ababeba4a21f3dba3da3523c670b207fb2feb62 <97b21ef57dfabbff660a4672c9fef7edfb720f47; 1ababeba4a21f3dba3da3523c670b207fb2feb62 <3ad7dca5e03bd64c65983a19734337512fd75491

The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.

Carried in the product catalogue

An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.

Linux — Linux

Does this concern one of your customers?

This page cannot answer that — it does not know your estate. Whoever has recorded their environments gets the answer the morning after publication, together with a paragraph they can forward to the customer unedited.

Try it for 28 days

Patchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.