From: Willem de Bruijn <willemdebruijn.kernel@gmail.com>
To: "Michael S. Tsirkin" <mst@redhat.com>,
Eric Dumazet <edumazet@kernel.org>
Cc: "David S . Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
Paolo Abeni <pabeni@redhat.com>,
Willem de Bruijn <willemb@google.com>,
Simon Horman <horms@kernel.org>,
netdev@vger.kernel.org, shaos <shawnq1@163.com>,
Jamal Hadi Salim <jhs@mojatatu.com>
Subject: Re: [PATCH net] net: harden qdisc_pkt_len_segs_init() against malicious GSO packets
Date: Thu, 22 Oct 2026 21:29:42 -0400 [thread overview]
Message-ID: <willemdebruijn.kernel.2d936272e7d49@gmail.com> (raw)
In-Reply-To: <20261022120246-mutt-send-email-mst@kernel.org>
Michael S. Tsirkin wrote:
> On Thu, Oct 22, 2026 at 05:54:36PM +0200, Eric Dumazet wrote:
> > An SKB_GSO_DODGY packet can carry untrusted gso_size and headers.
> >
> > For instance, gso_size=1 and hdr_len=65532 for a 524275-byte frame
> > makes qdisc_pkt_len_segs_init() compute an accounted length of
> > about 4,294,574,091 bytes (after gso_segs silently wrapped in a u16).
> >
> > With DRR quantum 256, the dequeue path then needs ~16.8 million
> > deficit refills before it can dequeue the skb, keeping the CPU in
> > the qdisc path long enough to trigger the soft-lockup watchdog.
> >
> > Commit 8f735d64382d ("net/sched: bound qdisc_pkt_len to prevent
> > qdisc soft lockup") added QDISC_PKT_LEN_MAX to bound size table
> > amplification. Use the same bound for DODGY packets:
> >
> > - Make gso_segs a u32 and drop packets whose segment count does
> > not fit GSO_MAX_SEGS, instead of silently truncating it.
> >
> > - Drop packets whose estimated qdisc_pkt_len() would exceed
> > QDISC_PKT_LEN_MAX.
> >
> > Fixes: 15e5a0307164 ("net_sched: better precise estimation on packet length for untrusted packets")
> > Reported-by: shaos <shawnq1@163.com>
> > Closes: https://lore.kernel.org/netdev/20261022144755.65025-1-shawnq1@163.com/
> > Signed-off-by: Eric Dumazet <edumazet@kernel.org>
> > Cc: Jamal Hadi Salim <jhs@mojatatu.com>
> > Cc: "Michael S. Tsirkin" <mst@redhat.com>
>
> I'm all for stack being more resilient.
>
> Acked-by: Michael S. Tsirkin <mst@redhat.com>
Reviewed-by: Willem de Bruijn <willemb@google.com>
next prev parent reply other threads:[~2026-10-23 1:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-22 15:54 [PATCH net] net: harden qdisc_pkt_len_segs_init() against malicious GSO packets Eric Dumazet
2026-10-22 16:03 ` Michael S. Tsirkin
2026-10-23 1:29 ` Willem de Bruijn [this message]
2026-10-26 23: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=willemdebruijn.kernel.2d936272e7d49@gmail.com \
--to=willemdebruijn.kernel@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=horms@kernel.org \
--cc=jhs@mojatatu.com \
--cc=kuba@kernel.org \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shawnq1@163.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.