CVE-2026-98096

ipv6: sr: restore network header before routing and forwarding

State
Published
Severity
7.4 High
Published
Sep 25, 2026
Updated
Oct 19, 2026
Reserved
Sep 25, 2026

Read the record on cve.org

Description

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.

Scores

CVSSScoreVectorSource
3.17.4 HighCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:HLinux

Weaknesses

The record names no weakness.

Affected Products

ProductVersions
LinuxLinux
  • 1ababeba4a21f3dba3da3523c670b207fb2feb62 to before f463c4786cf27376de7dfc0833a12e924a98f698Affected
  • 1ababeba4a21f3dba3da3523c670b207fb2feb62 to before 8f44d4160bcdb3136a9145a4b9c7816382976925Affected
  • 1ababeba4a21f3dba3da3523c670b207fb2feb62 to before 9cfbe2c381ab6d00a08e7a5b6028865adfb4e1bcAffected
  • 1ababeba4a21f3dba3da3523c670b207fb2feb62 to before af08f62b5a5a446d6134a92d86771d3d12e0e3daAffected
  • 1ababeba4a21f3dba3da3523c670b207fb2feb62 to before ce4c8beedc19aceeab0e7bdc6f34394fb158c47cAffected
  • 1ababeba4a21f3dba3da3523c670b207fb2feb62 to before 97b21ef57dfabbff660a4672c9fef7edfb720f47Affected
  • 1ababeba4a21f3dba3da3523c670b207fb2feb62 to before 3ad7dca5e03bd64c65983a19734337512fd75491Affected
  • 1ababeba4a21f3dba3da3523c670b207fb2feb62 to before 975b5b067f525a1b1338c4a3bee1c46545801518Affected
LinuxLinux
  • 4.10Affected
  • before 4.10Not affected
  • 5.10.271 through 5.10.*Not affected
  • 5.15.222 through 5.15.*Not affected
  • 6.1.189 through 6.1.*Not affected
  • 6.6.158 through 6.6.*Not affected
  • 6.12.111 through 6.12.*Not affected
  • 6.18.53 through 6.18.*Not affected
  • 7.2.7 through 7.2.*Not affected
  • 7.3 and laterNot affected

References

Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.