From: Pablo Neira Ayuso <pablo@netfilter.org>
To: netfilter-devel@vger.kernel.org
Cc: davem@davemloft.net, netdev@vger.kernel.org, kuba@kernel.org,
pabeni@redhat.com, edumazet@google.com, fw@strlen.de
Subject: [PATCH net,v2 0/4] Netfilter fixes for net
Date: Thu, 28 Nov 2024 13:38:36 +0100 [thread overview]
Message-ID: <20241128123840.49034-1-pablo@netfilter.org> (raw)
v2: Amended missing Fixes: tag in patch #4.
-o-
Hi,
The following patchset contains Netfilter fixes for net:
1) Fix esoteric UB due to uninitialized stack access in ip_vs_protocol_init(),
from Jinghao Jia.
2) Fix iptables xt_LED slab-out-of-bounds, reported by syzbot,
patch from Dmitry Antipov.
3) Remove WARN_ON_ONCE reachable from userspace to cap maximum cgroup
levels to 255, reported by syzbot.
4) Fix nft_inner incorrect use of percpu area to store tunnel parser
context with softirqs, reported by syzbot.
Please, pull these changes from:
git://git.kernel.org/pub/scm/linux/kernel/git/netfilter/nf.git nf-24-11-28
Thanks.
----------------------------------------------------------------
The following changes since commit 04f5cb48995d51deed0af71aaba1b8699511313f:
Documentation: tls_offload: fix typos and grammar (2024-11-28 12:09:06 +0100)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/netfilter/nf.git tags/nf-24-11-28
for you to fetch changes up to e4e12f81c14c8c0c5a2920587ad2619abf1b8e30:
netfilter: nft_inner: incorrect percpu area handling under softirq (2024-11-28 13:32:17 +0100)
----------------------------------------------------------------
netfilter pull request 24-11-28
----------------------------------------------------------------
Dmitry Antipov (1):
netfilter: x_tables: fix LED ID check in led_tg_check()
Jinghao Jia (1):
ipvs: fix UB due to uninitialized stack access in ip_vs_protocol_init()
Pablo Neira Ayuso (2):
netfilter: nft_socket: remove WARN_ON_ONCE on maximum cgroup level
netfilter: nft_inner: incorrect percpu area handling under softirq
include/net/netfilter/nf_tables_core.h | 1 +
net/netfilter/ipvs/ip_vs_proto.c | 4 +--
net/netfilter/nft_inner.c | 56 ++++++++++++++++++++++++++--------
net/netfilter/nft_socket.c | 2 +-
net/netfilter/xt_LED.c | 4 ++-
5 files changed, 50 insertions(+), 17 deletions(-)
next reply other threads:[~2024-11-28 12:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-28 12:38 Pablo Neira Ayuso [this message]
2024-11-28 12:38 ` [PATCH net 1/4] ipvs: fix UB due to uninitialized stack access in ip_vs_protocol_init() Pablo Neira Ayuso
2024-11-28 12:38 ` [PATCH net 2/4] netfilter: x_tables: fix LED ID check in led_tg_check() Pablo Neira Ayuso
2024-11-28 12:38 ` [PATCH net 3/4] netfilter: nft_socket: remove WARN_ON_ONCE on maximum cgroup level Pablo Neira Ayuso
2024-11-28 12:38 ` [PATCH net 4/4] netfilter: nft_inner: incorrect percpu area handling under softirq Pablo Neira Ayuso
2024-11-29 9:14 ` Eric Dumazet
2024-12-02 1:24 ` Pablo Neira Ayuso
2024-12-02 9:17 ` Eric Dumazet
2024-12-02 9:28 ` Pablo Neira Ayuso
2024-12-03 20:22 ` Pablo Neira Ayuso
2024-11-28 14:33 ` [PATCH net,v2 0/4] Netfilter fixes for net Paolo Abeni
2024-11-28 14:41 ` Pablo Neira Ayuso
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=20241128123840.49034-1-pablo@netfilter.org \
--to=pablo@netfilter.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=fw@strlen.de \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pabeni@redhat.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