All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yunsheng Lin <linyunsheng@huawei.com>
To: Paolo Abeni <pabeni@redhat.com>, <netdev@vger.kernel.org>
Cc: Dongseok Yi <dseok.yi@samsung.com>,
	Willem de Bruijn <willemb@google.com>
Subject: Re: [PATCH net-next] skbuff: revert "skbuff: remove some unnecessary operation in skb_segment_list()"
Date: Thu, 15 Apr 2021 10:23:17 +0800	[thread overview]
Message-ID: <cfb7af92-5a0b-059f-f598-be2c95f5419a@huawei.com> (raw)
In-Reply-To: <f092ecf89336221af04310c9feac800e49d4647f.1618397249.git.pabeni@redhat.com>

On 2021/4/14 18:48, Paolo Abeni wrote:
> the commit 1ddc3229ad3c ("skbuff: remove some unnecessary operation
> in skb_segment_list()") introduces an issue very similar to the
> one already fixed by commit 53475c5dd856 ("net: fix use-after-free when
> UDP GRO with shared fraglist").
> 
> If the GSO skb goes though skb_clone() and pskb_expand_head() before
> entering skb_segment_list(), the latter  will unshare the frag_list
> skbs and will release the old list. With the reverted commit in place,
> when skb_segment_list() completes, skb->next points to the just
> released list, and later on the kernel will hit UaF.

In that case, is "nskb->next = list_skb" needed before jumpping to
error when __skb_linearize() fails? As there is "nskb->next = list_skb"
before jumpping to error handling when skb_clone() fails.

The inconsistency above is the reason I sent the reverted patch:)

> 
> Note that since commit e0e3070a9bc9 ("udp: properly complete L4 GRO
> over UDP tunnel packet") the critical scenario can be reproduced also
> receiving UDP over vxlan traffic with:
> 
> NIC (NETIF_F_GRO_FRAGLIST enabled) -> vxlan -> UDP sink
> 
> Attaching a packet socket to the NIC will cause skb_clone() and the
> tunnel decapsulation will call pskb_expand_head().
> 
> Fixes: 1ddc3229ad3c ("skbuff: remove some unnecessary operation in skb_segment_list()")
> Signed-off-by: Paolo Abeni <pabeni@redhat.com>
> ---
>  net/core/skbuff.c | 15 ++++++++++++---
>  1 file changed, 12 insertions(+), 3 deletions(-)
> 
> diff --git a/net/core/skbuff.c b/net/core/skbuff.c
> index 3ad9e8425ab2..14010c0eec48 100644
> --- a/net/core/skbuff.c
> +++ b/net/core/skbuff.c
> @@ -3773,13 +3773,13 @@ struct sk_buff *skb_segment_list(struct sk_buff *skb,
>  	unsigned int tnl_hlen = skb_tnl_header_len(skb);
>  	unsigned int delta_truesize = 0;
>  	unsigned int delta_len = 0;
> +	struct sk_buff *tail = NULL;
>  	struct sk_buff *nskb, *tmp;
>  	int err;
>  
>  	skb_push(skb, -skb_network_offset(skb) + offset);
>  
>  	skb_shinfo(skb)->frag_list = NULL;
> -	skb->next = list_skb;
>  
>  	do {
>  		nskb = list_skb;
> @@ -3797,8 +3797,17 @@ struct sk_buff *skb_segment_list(struct sk_buff *skb,
>  			}
>  		}
>  
> -		if (unlikely(err))
> +		if (!tail)
> +			skb->next = nskb;
> +		else
> +			tail->next = nskb;
> +
> +		if (unlikely(err)) {
> +			nskb->next = list_skb;
>  			goto err_linearize;
> +		}
> +
> +		tail = nskb;
>  
>  		delta_len += nskb->len;
>  		delta_truesize += nskb->truesize;
> @@ -3825,7 +3834,7 @@ struct sk_buff *skb_segment_list(struct sk_buff *skb,
>  
>  	skb_gso_reset(skb);
>  
> -	skb->prev = nskb;
> +	skb->prev = tail;
>  
>  	if (skb_needs_linearize(skb, features) &&
>  	    __skb_linearize(skb))
> 


  parent reply	other threads:[~2021-04-15  2:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-14 10:48 [PATCH net-next] skbuff: revert "skbuff: remove some unnecessary operation in skb_segment_list()" Paolo Abeni
2021-04-14 21:10 ` patchwork-bot+netdevbpf
2021-04-15  2:23 ` Yunsheng Lin [this message]
2021-04-15  4:10   ` Dongseok Yi

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=cfb7af92-5a0b-059f-f598-be2c95f5419a@huawei.com \
    --to=linyunsheng@huawei.com \
    --cc=dseok.yi@samsung.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=willemb@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.