From: Paolo Abeni <pabeni@redhat.com>
To: Jiayuan Chen <jiayuan.chen@linux.dev>, netdev@vger.kernel.org
Cc: "David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@kernel.org>,
Jakub Kicinski <kuba@kernel.org>, Simon Horman <horms@kernel.org>,
Jonathan Corbet <corbet@lwn.net>,
Shuah Khan <skhan@linuxfoundation.org>,
Randy Dunlap <rdunlap@infradead.org>,
David Ahern <dsahern@kernel.org>,
Ido Schimmel <idosch@nvidia.com>,
Thomas Gleixner <tglx@kernel.org>,
Joel Granados <joel.granados@kernel.org>,
Fernando Fernandez Mancera <fmancera@suse.de>,
Petr Pavlu <petr.pavlu@suse.com>,
Kuniyuki Iwashima <kuniyu@google.com>,
Willem de Bruijn <willemb@google.com>,
Maoyi Xie <maoyi.xie@ntu.edu.sg>, Oleg Nesterov <oleg@redhat.com>,
Zhan Xusheng <zhanxusheng1024@gmail.com>,
Gerd Rausch <gerd.rausch@oracle.com>,
Nikolay Aleksandrov <razor@blackwall.org>,
Chia-Yu Chang <chia-yu.chang@nokia-bell-labs.com>,
Wyatt Feng <bronzed_45_vested@icloud.com>,
Hannes Frederic Sowa <hannes@stressinduktion.org>,
Flavio Leitner <fbl@redhat.com>, Petr Mladek <pmladek@suse.com>,
"Paul E. McKenney" <paulmck@kernel.org>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net v3 0/5] net: fix misc signed overflows caused by bad sysctl values
Date: Thu, 5 Nov 2026 12:05:50 +0100 [thread overview]
Message-ID: <1518ee19-95b3-4a13-b36d-5791324a6a23@redhat.com> (raw)
In-Reply-To: <20261101061331.286404-1-jiayuan.chen@linux.dev>
On 11/1/26 07:11, Jiayuan Chen wrote:
> Recently I have reviewed quite a few fixes for variable overflows caused
> by config values, i.e. a value set from sysctl, module params or netlink
> that is accepted as valid but later overflows when it is used in a
> calculation. I believe there are more of these still out there, so I
> used an LLM to dig through the code and it found the issues fixed in
> this series.
>
> All of them have been reproduced and verified in QEMU.
I think that the 'net' target + CC stable here is a bit too much.
The uAPI changes, even if reasonable, can still impact weird scenarios.
Targeting 'net-next' without CC ing stable would give time to
possibly catch such users.
Also issue predating git history and exploitable from root only
nowadays is a quite a good signal for net-next target.
If nobody opposes soonish I'll apply the series there.
/P
next prev parent reply other threads:[~2026-11-05 11:05 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-01 6:11 Jiayuan Chen
2026-11-01 6:11 ` [PATCH net v3 1/5] ipv6: restrict gc_elasticity to 31 Jiayuan Chen
2026-11-02 1:25 ` Hangbin Liu
2026-11-01 6:12 ` [PATCH net v3 2/5] ipv4: fix shift-out-of-bounds in ip_rt_send_redirect() Jiayuan Chen
2026-11-03 5:28 ` Kuniyuki Iwashima
2026-11-01 6:12 ` [PATCH net v3 3/5] ipv6: restrict mld_qrv to 255 Jiayuan Chen
2026-11-01 10:23 ` Nikolay Aleksandrov
2026-11-02 1:31 ` Hangbin Liu
2026-11-03 5:29 ` Kuniyuki Iwashima
2026-11-01 6:12 ` [PATCH net v3 4/5] ipv4: restrict igmp_qrv " Jiayuan Chen
2026-11-02 1:29 ` Hangbin Liu
2026-11-03 5:29 ` Kuniyuki Iwashima
2026-11-01 6:12 ` [PATCH net v3 5/5] net: restrict message_cost and message_burst to non-negative values Jiayuan Chen
2026-11-02 1:55 ` Hangbin Liu
2026-11-02 2:23 ` Jiayuan Chen
2026-11-02 3:32 ` Hangbin Liu
2026-11-03 5:30 ` Kuniyuki Iwashima
2026-11-05 11:05 ` Paolo Abeni [this message]
2026-11-06 12:20 ` [PATCH net v3 0/5] net: fix misc signed overflows caused by bad sysctl values 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=1518ee19-95b3-4a13-b36d-5791324a6a23@redhat.com \
--to=pabeni@redhat.com \
--cc=bronzed_45_vested@icloud.com \
--cc=chia-yu.chang@nokia-bell-labs.com \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@kernel.org \
--cc=fbl@redhat.com \
--cc=fmancera@suse.de \
--cc=gerd.rausch@oracle.com \
--cc=hannes@stressinduktion.org \
--cc=horms@kernel.org \
--cc=idosch@nvidia.com \
--cc=jiayuan.chen@linux.dev \
--cc=joel.granados@kernel.org \
--cc=kuba@kernel.org \
--cc=kuniyu@google.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maoyi.xie@ntu.edu.sg \
--cc=netdev@vger.kernel.org \
--cc=oleg@redhat.com \
--cc=paulmck@kernel.org \
--cc=petr.pavlu@suse.com \
--cc=pmladek@suse.com \
--cc=razor@blackwall.org \
--cc=rdunlap@infradead.org \
--cc=skhan@linuxfoundation.org \
--cc=tglx@kernel.org \
--cc=willemb@google.com \
--cc=zhanxusheng1024@gmail.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®