From: Jiayuan Chen <jiayuan.chen@linux.dev>
To: netdev@vger.kernel.org
Subject: Re: [PATCH net] net: fix frag_list leak in skb_segment_list() error path
Date: Thu, 22 Oct 2026 16:47:30 +0800 [thread overview]
Message-ID: <53109958-a182-4ec0-b7b4-e778b357ec50@linux.dev> (raw)
In-Reply-To: <20261021161858.761205-1-edumazet@kernel.org>
On 10/22/26 12:18 AM, Eric Dumazet wrote:
> skb_segment_list() detaches the frag_list from the head skb and moves
> its members one by one to the skb->next chain. On error, err_linearize
> frees that chain with kfree_skb_list(skb->next), relying on the members
> not yet processed to still be linked after the current one.
>
> This does not hold when the current member was shared: it is replaced
> by skb_clone(), and __skb_clone() clears ->next. If __skb_linearize()
> then fails on that clone, the remaining members are no longer reachable
> from skb->next nor from skb_shinfo(skb)->frag_list, and they leak.
>
> The skb_shared() error branch already relinks nskb->next to list_skb
> before jumping to err_linearize. Do it unconditionally right after nskb
> is added to the chain, so every error exit sees the remaining members.
> On the last member list_skb is NULL, which still terminates the chain.
>
> Fixes: 53475c5dd856 ("net: fix use-after-free when UDP GRO with shared fraglist")
> Signed-off-by: Eric Dumazet <edumazet@kernel.org>
> Cc: Simon Polack <spolack+git@mailbox.org>
Reviewed-by: Jiayuan Chen <jiayuan.chen@linux.dev>
> ---
> Bug discovered while reviewing at Simon Polack upcoming patch in
> skb_segment_list()
>
> net/core/skbuff.c | 9 ++++++---
> 1 file changed, 6 insertions(+), 3 deletions(-)
>
> diff --git a/net/core/skbuff.c b/net/core/skbuff.c
> index ab178af02a2262d65175daff7f093c85eaa09c92..beddbf6812b9f387672c7ab5f0a1c07ab9bd0806 100644
> --- a/net/core/skbuff.c
> +++ b/net/core/skbuff.c
> @@ -4734,10 +4734,13 @@ struct sk_buff *skb_segment_list(struct sk_buff *skb,
> else
> tail->next = nskb;
>
> - if (unlikely(err)) {
> - nskb->next = list_skb;
> + /* nskb may be a clone with a NULL ->next: keep the remaining
> + * members linked so that err_linearize frees them.
> + */
> + nskb->next = list_skb;
> +
> + if (unlikely(err))
> goto err_linearize;
> - }
>
> tail = nskb;
>
next prev parent reply other threads:[~2026-10-22 8:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-21 16:18 [PATCH net] net: fix frag_list leak in skb_segment_list() error path Eric Dumazet
2026-10-21 16:54 ` Willem de Bruijn
2026-10-22 4:35 ` Wang Zhan
2026-10-22 8:47 ` Jiayuan Chen [this message]
2026-10-23 21:30 ` 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=53109958-a182-4ec0-b7b4-e778b357ec50@linux.dev \
--to=jiayuan.chen@linux.dev \
--cc=netdev@vger.kernel.org \
/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