CVE-2026-98096ipv6: sr: restore network header before routing and forwarding
Updated under an hour ago ()
Does this affect you?
It affects Linux. Add what you run to find out whether that includes you.
No exploitation reported and no EPSS estimate yet.
Do this next
Free account, 1 product
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.
- CVSS
- 7.4 HIGH (v3.1, CNA)CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:H
- Weakness (CWE)
- Not given
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- Not loaded for this CVE
- Assigned by
- Linux
- NVD analysis
- Undergoing Analysis
- Record last updated
- Oct 3, 2026
- First seen by InfoSec Signals
- Oct 9, 2026
Affected products
Linux Linux linux:linux (from the name) | from 1ababeba4a21f3dba3da3523c670b207fb2feb62 before f463c4786cf27376de7dfc0833a12e924a98f698; from 1ababeba4a21f3dba3da3523c670b207fb2feb62 before 8f44d4160bcdb3136a9145a4b9c7816382976925; from 1ababeba4a21f3dba3da3523c670b207fb2feb62 before 9cfbe2c381ab6d00a08e7a5b6028865adfb4e1bc; from 1ababeba4a21f3dba3da3523c670b207fb2feb62 before af08f62b5a5a446d6134a92d86771d3d12e0e3da; from 1ababeba4a21f3dba3da3523c670b207fb2feb62 before ce4c8beedc19aceeab0e7bdc6f34394fb158c47c; from 1ababeba4a21f3dba3da3523c670b207fb2feb62 before 97b21ef57dfabbff660a4672c9fef7edfb720f47; from 1ababeba4a21f3dba3da3523c670b207fb2feb62 before 3ad7dca5e03bd64c65983a19734337512fd75491; from 1ababeba4a21f3dba3da3523c670b207fb2feb62 before 975b5b067f525a1b1338c4a3bee1c46545801518 | CNA record |
References
- https://git.kernel.org/stable/c/f463c4786cf27376de7dfc0833a12e924a98f698
- https://git.kernel.org/stable/c/8f44d4160bcdb3136a9145a4b9c7816382976925
- https://git.kernel.org/stable/c/9cfbe2c381ab6d00a08e7a5b6028865adfb4e1bc
- https://git.kernel.org/stable/c/af08f62b5a5a446d6134a92d86771d3d12e0e3da
- https://git.kernel.org/stable/c/ce4c8beedc19aceeab0e7bdc6f34394fb158c47c
- https://git.kernel.org/stable/c/97b21ef57dfabbff660a4672c9fef7edfb720f47
- https://git.kernel.org/stable/c/3ad7dca5e03bd64c65983a19734337512fd75491
- https://git.kernel.org/stable/c/975b5b067f525a1b1338c4a3bee1c46545801518
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.