From: Ido Schimmel <idosch@nvidia.com>
To: Eric Dumazet <edumazet@google.com>
Cc: "David S . Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Simon Horman <horms@kernel.org>, David Ahern <dsahern@kernel.org>,
netdev@vger.kernel.org, eric.dumazet@gmail.com,
Oskar Kjos <oskar.kjos@hotmail.com>
Subject: Re: [PATCH net] ipv6: icmp: clear skb2->cb[] in ip6_err_gen_icmpv6_unreach()
Date: Fri, 27 Mar 2026 20:54:28 +0300 [thread overview]
Message-ID: <20260327175428.GA1152445@shredder> (raw)
In-Reply-To: <20260326202608.2976021-1-edumazet@google.com>
On Thu, Mar 26, 2026 at 08:26:08PM +0000, Eric Dumazet wrote:
> 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?
>
> Should the cb array also be cleared in ip6_err_gen_icmpv6_unreach() and
> ip6ip6_err() to prevent this?
>
> This patch implements the first suggestion.
>
> I am not sure if ip6ip6_err() needs to be changed.
> A separate patch would be better anyway.
>
> Fixes: ca15a078bd90 ("sit: generate icmpv6 error when receiving icmpv4 error")
> Reported-by: Ido Schimmel <idosch@nvidia.com>
> Closes: https://sashiko.dev/#/patchset/20260326155138.2429480-1-edumazet%40google.com
> Signed-off-by: Eric Dumazet <edumazet@google.com>
> Cc: Ido Schimmel <idosch@nvidia.com>
> Cc: Oskar Kjos <oskar.kjos@hotmail.com>
Reviewed-by: Ido Schimmel <idosch@nvidia.com>
prev parent reply other threads:[~2026-03-27 17:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-26 20:26 [PATCH net] ipv6: icmp: clear skb2->cb[] in ip6_err_gen_icmpv6_unreach() Eric Dumazet
2026-03-27 17:54 ` Ido Schimmel [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260327175428.GA1152445@shredder \
--to=idosch@nvidia.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=eric.dumazet@gmail.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=oskar.kjos@hotmail.com \
--cc=pabeni@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox