From: Fernando Fernandez Mancera <fmancera@suse.de>
To: Anton Danilov <littlesmilingcloud@gmail.com>, netdev@vger.kernel.org
Cc: "David S . Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Simon Horman <horms@kernel.org>, David Ahern <dsahern@kernel.org>,
Ido Schimmel <idosch@nvidia.com>,
Alexei Starovoitov <ast@kernel.org>, Thomas Graf <tgraf@suug.ch>,
Daniel Borkmann <daniel@iogearbox.net>,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH net] ipip: fix skb leak in collect_md mode when metadata_dst allocation fails
Date: Wed, 19 Aug 2026 13:47:02 +0200 [thread overview]
Message-ID: <3d78b662-85da-4571-9e6a-168bc5f43f7a@suse.de> (raw)
In-Reply-To: <20260819104338.432631-2-littlesmilingcloud@gmail.com>
On 8/19/26 12:43 PM, Anton Danilov wrote:
> In collect_md mode ipip_tunnel_rcv() returns 0 without freeing the skb
> when ip_tun_rx_dst() fails to allocate the metadata_dst. ipip_rcv() and
> mplsip_rcv() are registered as xfrm_tunnel handlers, so tunnel4_rcv()
> and tunnelmpls4_rcv() read the zero return as "the packet has been
> consumed" and do not free it either. The skb is leaked.
>
> The other tunnel drivers all dispose of the packet at this point:
> ip6_tunnel.c jumps to its drop label, ip_gre.c and ip6_gre.c return
> PACKET_REJECT, which makes gre_rcv() free the skb. Only ipip returns 0.
>
> Jump to the existing drop label instead. It frees the skb and still
> returns 0, so the packet keeps being reported as consumed, which is what
> we want here: the outer header has already been pulled, and neither the
> remaining handlers nor an ICMP unreachable have any use for it.
>
> Triggering this needs an ipip or mplsip tunnel in collect_md mode and an
> atomic allocation failure, which is why it has gone unnoticed.
>
> Fixes: cfc7381b3002 ("ip_tunnel: add collect_md mode to IPIP tunnel")
> Cc: stable@vger.kernel.org
> Assisted-by: Claude-Code:claude-opus-5
> Signed-off-by: Anton Danilov <littlesmilingcloud@gmail.com>
> ---
> net/ipv4/ipip.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/net/ipv4/ipip.c b/net/ipv4/ipip.c
> index b643194f57d2..ddf62b45566b 100644
> --- a/net/ipv4/ipip.c
> +++ b/net/ipv4/ipip.c
> @@ -248,7 +248,7 @@ static int ipip_tunnel_rcv(struct sk_buff *skb, u8 ipproto)
>
> tun_dst = ip_tun_rx_dst(skb, flags, 0, 0);
> if (!tun_dst)
> - return 0;
> + goto drop;
> ip_tunnel_md_udp_encap(skb, &tun_dst->u.tun_info);
> }
> skb_reset_mac_header(skb);
Reviewed-by: Fernando Fernandez Mancera <fmancera@suse.de>
Thanks!
next prev parent reply other threads:[~2026-08-19 11:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-19 10:43 Anton Danilov
2026-08-19 11:47 ` Fernando Fernandez Mancera [this message]
2026-08-22 20:10 ` patchwork-bot+netdevbpf
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=3d78b662-85da-4571-9e6a-168bc5f43f7a@suse.de \
--to=fmancera@suse.de \
--cc=ast@kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=idosch@nvidia.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=littlesmilingcloud@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=stable@vger.kernel.org \
--cc=tgraf@suug.ch \
/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
all inboxes | Powered by JetHome®