ipv6: icmp: clear skb2->cb[] in ip6_err_gen_icmpv6_unreach()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ ca15a078bd907df5fc1c009477869c5cbde3b753 · < a2edbb6393972a02114b6003953a5cef3104fada| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
ipv6: icmp: clear skb2->cb[] in ip6_err_gen_icmpv6_unreach()
Sashiko AI-review observed:
In ip6_err_gen_icmpv6_unreach(), the skb is an outer IPv4 ICMP error packet where its cb contains an IPv4 inet_skb_parm. When skb is cloned into skb2 and passed to icmp6_send(), it uses IP6CB(skb2).
IP6CB interprets the IPv4 inet_skb_parm as an inet6_skb_parm. The cipso offset in inet_skb_parm.opt directly overlaps with dsthao in inet6_skb_parm at offset 18.
If an attacker sends a forged ICMPv4 error with a CIPSO IP option, dsthao would be a non-zero offset. Inside icmp6_send(), mip6_addr_swap() is called and uses ipv6_find_tlv(skb, opt->dsthao, IPV6_TLV_HAO).
This would scan the inner, attacker-controlled IPv6 packet starting at that offset, potentially returning a fake TLV without checking if the remaining packet length can hold the full 18-byte struct ipv6_destopt_hao.
Could mip6_addr_swap() then perform a 16-byte swap that extends past the end of the packet data into skb_shared_info?
From the CVE record · Linux
The Linux kernel’s IPv6 ICMP error handling can misinterpret control data copied from an IPv4 ICMP error packet. A remote attacker who sends a forged ICMPv4 error with a CIPSO IP option and attacker-controlled inner IPv6 packet could potentially trigger a write past the packet data. No authentication or user interaction is described.
Operators running Linux kernels should check whether their kernel includes the fix for CVE-2026-43038; affected versions are not specified.