Skip to main content

kernel

The Linux kernel — the core of the OS that runs every container and drives the hardware.

Version: 6.18.49

Type: Kernel

License:

  • 3576
    • C 0
    • H 1
    • M 2
    • L 2
  • T 3581

CVE-2026-98096 is no longer reported for kernel in the newest 1.36 release (v10). View kernel in v10

CVE-2026-98096

NVD

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.

Not affected High

Our assessment

The vulnerable code is never executed

The defect is in IPv6 segment-routing header processing, which is disabled per interface by default. Enabling it needs administrative privilege, and until then incoming segment-routing packets are discarded, so the affected code does not run.

Syself Security
CVE-2026-98096 across every release View all 3581 findings in kernel