linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jason Wang <jasowang@redhat.com>
To: Bui Quang Minh <minhquangbui99@gmail.com>
Cc: netdev@vger.kernel.org, "Michael S. Tsirkin" <mst@redhat.com>,
	"Xuan Zhuo" <xuanzhuo@linux.alibaba.com>,
	"Eugenio Pérez" <eperezma@redhat.com>,
	"Andrew Lunn" <andrew+netdev@lunn.ch>,
	"David S. Miller" <davem@davemloft.net>,
	"Eric Dumazet" <edumazet@google.com>,
	"Jakub Kicinski" <kuba@kernel.org>,
	"Paolo Abeni" <pabeni@redhat.com>, "Gavin Li" <gavinl@nvidia.com>,
	"Gavi Teitz" <gavi@nvidia.com>, "Parav Pandit" <parav@nvidia.com>,
	virtualization@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net] virtio-net: fix received length check in big packets
Date: Mon, 7 Jul 2025 11:49:06 +0800	[thread overview]
Message-ID: <CACGkMEvBf3_cReVDxX2dRALrS=fQvg9pMY1LKwmbf=Gp9zSTPQ@mail.gmail.com> (raw)
In-Reply-To: <CACGkMEvCZ1D7k+=V-Ta9hXpdW4ofnbXfQ4JcADXabC13CA884A@mail.gmail.com>

On Mon, Jul 7, 2025 at 11:48 AM Jason Wang <jasowang@redhat.com> wrote:
>
> On Sun, Jul 6, 2025 at 10:12 PM Bui Quang Minh <minhquangbui99@gmail.com> wrote:
> >
> > Since commit 4959aebba8c0 ("virtio-net: use mtu size as buffer length
> > for big packets"), the allocated size for big packets is not
> > MAX_SKB_FRAGS * PAGE_SIZE anymore but depends on negotiated MTU. The
> > number of allocated frags for big packets is stored in
> > vi->big_packets_num_skbfrags. This commit fixes the received length
> > check corresponding to that change. The current incorrect check can lead
> > to NULL page pointer dereference in the below while loop when erroneous
> > length is received.
> >
> > Fixes: 4959aebba8c0 ("virtio-net: use mtu size as buffer length for big packets")
> > Signed-off-by: Bui Quang Minh <minhquangbui99@gmail.com>
> > ---
> >  drivers/net/virtio_net.c | 10 +++++++---
> >  1 file changed, 7 insertions(+), 3 deletions(-)
> >
> > diff --git a/drivers/net/virtio_net.c b/drivers/net/virtio_net.c
> > index 5d674eb9a0f2..ead1cd2fb8af 100644
> > --- a/drivers/net/virtio_net.c
> > +++ b/drivers/net/virtio_net.c
> > @@ -823,7 +823,7 @@ static struct sk_buff *page_to_skb(struct virtnet_info *vi,
> >  {
> >         struct sk_buff *skb;
> >         struct virtio_net_common_hdr *hdr;
> > -       unsigned int copy, hdr_len, hdr_padded_len;
> > +       unsigned int copy, hdr_len, hdr_padded_len, max_remaining_len;
> >         struct page *page_to_free = NULL;
> >         int tailroom, shinfo_size;
> >         char *p, *hdr_p, *buf;
> > @@ -887,12 +887,16 @@ static struct sk_buff *page_to_skb(struct virtnet_info *vi,
> >          * tries to receive more than is possible. This is usually
> >          * the case of a broken device.
> >          */
> > -       if (unlikely(len > MAX_SKB_FRAGS * PAGE_SIZE)) {
> > +       BUG_ON(offset >= PAGE_SIZE);
> > +       max_remaining_len = (unsigned int)PAGE_SIZE - offset;
> > +       max_remaining_len += vi->big_packets_num_skbfrags * PAGE_SIZE;
> > +       if (unlikely(len > max_remaining_len)) {
> >                 net_dbg_ratelimited("%s: too much data\n", skb->dev->name);
> >                 dev_kfree_skb(skb);
> > +               give_pages(rq, page);
>
> Should this be an independent fix?

Btw, the page_to_skb() is really kind of messed up right now that it
is used by both big and mergeable. We may need to consider splitting
the logic in the future.

Thanks

>
> >                 return NULL;
> >         }
> > -       BUG_ON(offset >= PAGE_SIZE);
> > +
> >         while (len) {
> >                 unsigned int frag_size = min((unsigned)PAGE_SIZE - offset, len);
> >                 skb_add_rx_frag(skb, skb_shinfo(skb)->nr_frags, page, offset,
> > --
> > 2.43.0
> >
>
> Thanks


  reply	other threads:[~2025-07-07  3:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-06 14:11 [PATCH net] virtio-net: fix received length check in big packets Bui Quang Minh
2025-07-07  3:48 ` Jason Wang
2025-07-07  3:49   ` Jason Wang [this message]
2025-07-08 14:26   ` Bui Quang Minh
2025-07-08 14:30     ` Bui Quang Minh

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='CACGkMEvBf3_cReVDxX2dRALrS=fQvg9pMY1LKwmbf=Gp9zSTPQ@mail.gmail.com' \
    --to=jasowang@redhat.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=eperezma@redhat.com \
    --cc=gavi@nvidia.com \
    --cc=gavinl@nvidia.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=minhquangbui99@gmail.com \
    --cc=mst@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=parav@nvidia.com \
    --cc=virtualization@lists.linux.dev \
    --cc=xuanzhuo@linux.alibaba.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;
as well as URLs for NNTP newsgroup(s).