ipv6: sr: restore network header before routing and forwarding
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 1%. Fixed in Kernel 3ad7dca5e03bd64c65983a19734337512fd75491, Kernel 8f44d4160bcdb3136a9145a4b9c7816382976925, Kernel 975b5b067f525a1b1338c4a3bee1c46545801518 and 5 more.
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.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =4.10, >=1ababeba4a21f3dba3da3523c670b207fb2feb62 <3ad7dca5e03bd64c65983a19734337512fd75491, >=1ababeba4a21f3dba3da3523c670b207fb2feb62 <8f44d4160bcdb3136a9145a4b9c7816382976925, >=1ababeba4a21f3dba3da3523c670b207fb2feb62 <975b5b067f525a1b1338c4a3bee1c46545801518, >=1ababeba4a21f3dba3da3523c670b207fb2feb62 <97b21ef57dfabbff660a4672c9fef7edfb720f47, >=1ababeba4a21f3dba3da3523c670b207fb2feb62 <9cfbe2c381ab6d00a08e7a5b6028865adfb4e1bc, >=1ababeba4a21f3dba3da3523c670b207fb2feb62 <af08f62b5a5a446d6134a92d86771d3d12e0e3da, >=1ababeba4a21f3dba3da3523c670b207fb2feb62 <ce4c8beedc19aceeab0e7bdc6f34394fb158c47c, >=1ababeba4a21f3dba3da3523c670b207fb2feb62 <f463c4786cf27376de7dfc0833a12e924a98f698 | 3ad7dca5e03bd64c65983a19734337512fd75491, 8f44d4160bcdb3136a9145a4b9c7816382976925, 975b5b067f525a1b1338c4a3bee1c46545801518, 97b21ef57dfabbff660a4672c9fef7edfb720f47, 9cfbe2c381ab6d00a08e7a5b6028865adfb4e1bc, af08f62b5a5a446d6134a92d86771d3d12e0e3da, ce4c8beedc19aceeab0e7bdc6f34394fb158c47c, f463c4786cf27376de7dfc0833a12e924a98f698 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket