From: Willem de Bruijn <willemdebruijn.kernel@gmail.com>
To: Dongli Zhang <dongli.zhang@oracle.com>,
Willem de Bruijn <willemdebruijn.kernel@gmail.com>,
Weiming Shi <bestswngs@gmail.com>,
netdev@vger.kernel.org
Cc: jasowang@redhat.com, pabeni@redhat.com, kuba@kernel.org,
edumazet@google.com, xmei5@asu.edu,
linux-kernel@vger.kernel.org,
Si-Wei Liu <si-wei.liu@oracle.com>
Subject: Re: [PATCH net] tun: free page on short-frame rejection in tun_xdp_one()
Date: Wed, 20 May 2026 20:58:28 -0400 [thread overview]
Message-ID: <willemdebruijn.kernel.7526a484e05@gmail.com> (raw)
In-Reply-To: <3f4460b0-fd07-40f6-a9c6-827dd0ce2ff8@oracle.com>
Dongli Zhang wrote:
>
>
> On 2026-05-20 5:05 PM, Willem de Bruijn wrote:
> > Weiming Shi wrote:
> >> tun_xdp_one() returns -EINVAL on a frame shorter than ETH_HLEN without
> >> freeing the page that vhost_net_build_xdp() allocated for it.
> >> tun_sendmsg() discards that -EINVAL and still returns total_len, so
> >> vhost_tx_batch() takes the success path and never frees the page; each
> >> short frame in a batch leaks one page-frag chunk.
> >>
> >> A local process that can open /dev/net/tun and /dev/vhost-net can hit
> >> this path: it attaches a tun/tap device as the vhost-net backend and
> >> feeds TX descriptors whose length minus the virtio-net header is below
> >> ETH_HLEN. Each kick leaks the page-frag chunks for that batch, and a
> >> tight submission loop exhausts host memory and triggers an OOM panic.
> >> Free the page before returning -EINVAL, matching the XDP-program error
> >> path in the same function.
> >>
> >> Fixes: 049584807f1d ("tun: add missing verification for short frame")
> >> Reported-by: Xiang Mei <xmei5@asu.edu>
> >> Assisted-by: Claude:claude-opus-4-7
> >> Signed-off-by: Weiming Shi <bestswngs@gmail.com>
> >> ---
> >> drivers/net/tun.c | 4 +++-
> >> 1 file changed, 3 insertions(+), 1 deletion(-)
> >>
> >> diff --git a/drivers/net/tun.c b/drivers/net/tun.c
> >> index b183189f1853..f594360d66d6 100644
> >> --- a/drivers/net/tun.c
> >> +++ b/drivers/net/tun.c
> >> @@ -2394,8 +2394,10 @@ static int tun_xdp_one(struct tun_struct *tun,
> >> bool skb_xdp = false;
> >> struct page *page;
> >>
> >> - if (unlikely(datasize < ETH_HLEN))
> >> + if (unlikely(datasize < ETH_HLEN)) {
> >> + put_page(virt_to_head_page(xdp->data));
> >> return -EINVAL;
> >> + }
> >
> > Make sense, thanks.
> >
> > The error path from tun_xdp_act does the same. And the default: label
> > used to too, before a batching optimization was introduced.
> >
> > Is the same then also missing if build_skb fails?
> >
>
> I also agree that we may need to handle build_skb() failure.
Thanks. Fine to defer to a separate patch btw. Either way.
> In addition, I think we may need this fix for tap_get_user_xdp() as well.
>
> Thank you very much!
>
> Dongli Zhang
prev parent reply other threads:[~2026-05-21 0:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-20 16:00 [PATCH net] tun: free page on short-frame rejection in tun_xdp_one() Weiming Shi
2026-05-21 0:05 ` Willem de Bruijn
2026-05-21 0:37 ` Dongli Zhang
2026-05-21 0:58 ` Willem de Bruijn [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=willemdebruijn.kernel.7526a484e05@gmail.com \
--to=willemdebruijn.kernel@gmail.com \
--cc=bestswngs@gmail.com \
--cc=dongli.zhang@oracle.com \
--cc=edumazet@google.com \
--cc=jasowang@redhat.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=si-wei.liu@oracle.com \
--cc=xmei5@asu.edu \
/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