From: Andrew Lunn <andrew@lunn.ch>
To: shaos <shawnq1@163.com>
Cc: jhs@mojatatu.com, Jiri Pirko <jiri@resnulli.us>,
"David S . Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Simon Horman <horms@kernel.org>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
security@kernel.org
Subject: Re: [BUG] net/sched: act_csum can checksum beyond a short IPv6 jumbogram skb
Date: Thu, 22 Oct 2026 17:36:18 +0200 [thread overview]
Message-ID: <76f5a903-90cc-4eeb-8afc-99b5cd89b75d@lunn.ch> (raw)
In-Reply-To: <20261022144653.60550-1-shawnq1@163.com>
On Thu, Oct 22, 2026 at 02:46:53PM +0000, shaos wrote:
> Hello,
>
> An unprivileged process with namespace-scoped CAP_NET_ADMIN and CAP_NET_RAW installs a csum action for UDP-Lite and sends a 300-byte IPv6 frame with a Jumbo Payload value of 0xffffffca and UDP-Lite coverage longer than the bytes present. The jumbo-length addition wraps the pull-length check, while the later checksum path still uses the unwrapped length.
Please configure your editor to wrap lines at around 70
characters. Standard netiquette rules should be used on mailing lists.
Flooding the netdev list with bug reports like this will just result
in them being directed to /dev/null.
If you want to do something useful, fix the issue. Please do it
slowly, one bug report at a time, so you can learn how to do it
correctly without wasting peoples time.
Andrew
next prev parent reply other threads:[~2026-10-22 15:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-22 14:46 shaos
2026-10-22 15:36 ` Andrew Lunn [this message]
2026-10-22 15:46 ` Jamal Hadi Salim
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=76f5a903-90cc-4eeb-8afc-99b5cd89b75d@lunn.ch \
--to=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=security@kernel.org \
--cc=shawnq1@163.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
all inboxes | Powered by JetHome®