ipv6: sit: reload inner IPv6 header after GSO offloads
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 14909664e4e192f4c6f6fcdccd9919af7cf783ab · < 2fa49b2715e1bad12ce3b0fa64e234d9582c8193| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
ipv6: sit: reload inner IPv6 header after GSO offloads
ipip6_tunnel_xmit() caches the inner IPv6 header pointer at function entry and continues using it after iptunnel_handle_offloads().
For GSO skbs, iptunnel_handle_offloads() calls skb_header_unclone(). When the skb header is cloned, skb_header_unclone() can call pskb_expand_head(), which may move the skb head. The pskb_expand_head() contract requires pointers into the skb header to be reloaded after the call.
If the later skb_realloc_headroom() branch is not taken, SIT uses the stale iph6 pointer to read the inner hop limit and DS field. That can read from a freed skb head after the old head's remaining clone is released.
Reload iph6 after the offload helper succeeds and before subsequent reads from the inner IPv6 header. Keep the existing reload after skb_realloc_headroom(), since that branch can also replace the skb.
From the CVE record · Linux
The Linux kernel’s IPv6 SIT transmit path can retain a pointer to an inner IPv6 header after GSO offload handling moves the packet header. If the header is cloned and a later headroom reallocation does not occur, reading the hop limit or DS field can access freed memory. The input does not specify attacker access, authentication, or user-interaction requirements.
Engineers running Linux kernels with IPv6 SIT should check their kernel versions; affected versions are not specified.