From: patchwork-bot+netdevbpf@kernel.org
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: netfilter-devel@vger.kernel.org, davem@davemloft.net,
netdev@vger.kernel.org, kuba@kernel.org, pabeni@redhat.com,
edumazet@google.com, fw@strlen.de
Subject: Re: [PATCH net 1/2] netfilter: iptables: Fix null-ptr-deref in iptable_nat_table_init().
Date: Thu, 01 Aug 2024 10:20:32 +0000 [thread overview]
Message-ID: <172250763233.8894.11448540825840373569.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240731213046.6194-2-pablo@netfilter.org>
Hello:
This series was applied to netdev/net.git (main)
by Pablo Neira Ayuso <pablo@netfilter.org>:
On Wed, 31 Jul 2024 23:30:45 +0200 you wrote:
> From: Kuniyuki Iwashima <kuniyu@amazon.com>
>
> We had a report that iptables-restore sometimes triggered null-ptr-deref
> at boot time. [0]
>
> The problem is that iptable_nat_table_init() is exposed to user space
> before the kernel fully initialises netns.
>
> [...]
Here is the summary with links:
- [net,1/2] netfilter: iptables: Fix null-ptr-deref in iptable_nat_table_init().
https://git.kernel.org/netdev/net/c/5830aa863981
- [net,2/2] netfilter: iptables: Fix potential null-ptr-deref in ip6table_nat_table_init().
https://git.kernel.org/netdev/net/c/c22921df777d
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2024-08-01 10:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-31 21:30 [PATCH net 0/2] Netfilter fixes for net Pablo Neira Ayuso
2024-07-31 21:30 ` [PATCH net 1/2] netfilter: iptables: Fix null-ptr-deref in iptable_nat_table_init() Pablo Neira Ayuso
2024-08-01 10:20 ` patchwork-bot+netdevbpf [this message]
2024-07-31 21:30 ` [PATCH net 2/2] netfilter: iptables: Fix potential null-ptr-deref in ip6table_nat_table_init() 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=172250763233.8894.11448540825840373569.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.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 \
--cc=pablo@netfilter.org \
/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.