ip6_tunnel: use skb_cow_head() in ip6_tnl_xmit()
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 37df5bc6b5ccad88c2faa0f5466f150178882b74, Kernel 629d5557e635cdbc109a14ed913ba5a540e3f79a, Kernel 6e8eff8ed13b14708bc39f170144eacde494aac6 and 5 more.
In the Linux kernel, the following vulnerability has been resolved: ip6_tunnel: use skb_cow_head() in ip6_tnl_xmit() ip6_tnl_xmit() may need to expand headroom before it can push the outer IPv6 and optional encap headers. It currently does that with skb_realloc_headroom(), copies skb->sk ownership, consumes the original skb, and then continues processing with the replacement skb kept only in its local variable. That is safe only if the helper cannot fail afterwards. But this helper still has post-reallocation error exits. collect_md tunnels reject non-NONE encap after the replacement, and ip6_tnl_encap() can also fail later. In those cases the helper returns an error to its callers while the caller still only has the original skb pointer. Both ip6_tnl_start_xmit() and the IPv6 GRE paths free the caller skb on error, so they can end up freeing an skb that ip6_tnl_xmit() already consumed. Use skb_cow_head() instead. It provides the required headroom and writability without privately replacing the caller-owned skb, so later error returns cannot leave callers with a stale pointer. The Ethernet users, ip6gretap and ip6erspan, clear IFF_TX_SKB_SHARING and already call skb_cow_head() before entering ip6_tnl_xmit(). They do not rely on the removed skb_shared() reallocation. This also makes the IPv6 tunnel path consistent with ip_tunnel_xmit().
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =4.7, >=058214a4d1dfefed9f01a277fadd3590acb5f990 <37df5bc6b5ccad88c2faa0f5466f150178882b74, >=058214a4d1dfefed9f01a277fadd3590acb5f990 <629d5557e635cdbc109a14ed913ba5a540e3f79a, >=058214a4d1dfefed9f01a277fadd3590acb5f990 <6e8eff8ed13b14708bc39f170144eacde494aac6, >=058214a4d1dfefed9f01a277fadd3590acb5f990 <87f21b59ddc618eff9670c174842964ad65fdade, >=058214a4d1dfefed9f01a277fadd3590acb5f990 <8fc56ca49fc0ee1725b55c67bb43ab0dd01f3f52, >=058214a4d1dfefed9f01a277fadd3590acb5f990 <b36dfd6e8cff00cea81c11cc0af88d1564763461, >=058214a4d1dfefed9f01a277fadd3590acb5f990 <dc1a319a4815c074914e2812e0e9cd0164ca682b, >=058214a4d1dfefed9f01a277fadd3590acb5f990 <defa0adeff132cc90ed66915b9a104d9393e1e54 | 37df5bc6b5ccad88c2faa0f5466f150178882b74, 629d5557e635cdbc109a14ed913ba5a540e3f79a, 6e8eff8ed13b14708bc39f170144eacde494aac6, 87f21b59ddc618eff9670c174842964ad65fdade, 8fc56ca49fc0ee1725b55c67bb43ab0dd01f3f52, b36dfd6e8cff00cea81c11cc0af88d1564763461, dc1a319a4815c074914e2812e0e9cd0164ca682b, defa0adeff132cc90ed66915b9a104d9393e1e54 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket