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, horms@kernel.org
Subject: Re: [PATCH net 1/8] netfilter: revalidate bridge ports
Date: Thu, 11 Jun 2026 10:40:14 +0000 [thread overview]
Message-ID: <178117441489.3886909.15763136255322020254.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260610161629.214092-2-pablo@netfilter.org>
Hello:
This series was applied to netdev/net.git (main)
by Pablo Neira Ayuso <pablo@netfilter.org>:
On Wed, 10 Jun 2026 18:16:21 +0200 you wrote:
> From: Florian Westphal <fw@strlen.de>
>
> ebt_redirect_tg() dereferences br_port_get_rcu() return without a
> NULL check, causing a kernel panic when the bridge port has been
> removed between the original hook invocation and an NFQUEUE
> reinject.
>
> [...]
Here is the summary with links:
- [net,1/8] netfilter: revalidate bridge ports
https://git.kernel.org/netdev/net/c/ccb9fd4b8753
- [net,2/8] netfilter: nf_tables_offload: drop device refcount on error
https://git.kernel.org/netdev/net/c/efc542561729
- [net,3/8] netfilter: nf_conntrack: destroy stale expectfn expectations on unregister
https://git.kernel.org/netdev/net/c/c3009418f9fa
- [net,4/8] netfilter: x_tables: avoid leaking percpu counter pointers
https://git.kernel.org/netdev/net/c/f7f2fbb0e893
- [net,5/8] netfilter: nf_log: validate MAC header was set before dumping it
https://git.kernel.org/netdev/net/c/a84b6fedbc97
- [net,6/8] netfilter: nft_exthdr: fix register tracking for F_PRESENT flag
https://git.kernel.org/netdev/net/c/772cecf198da
- [net,7/8] netfilter: nft_fib: fix stale stack leak via the OIFNAME register
https://git.kernel.org/netdev/net/c/ab185e0c4fb8
- [net,8/8] netfilter: nft_meta_bridge: fix stale stack leak via IIFHWADDR register
https://git.kernel.org/netdev/net/c/c7d573551f92
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:[~2026-06-11 10:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-10 16:16 [PATCH net 0/8] Netfilter fixes for net Pablo Neira Ayuso
2026-06-10 16:16 ` [PATCH net 1/8] netfilter: revalidate bridge ports Pablo Neira Ayuso
2026-06-11 10:40 ` patchwork-bot+netdevbpf [this message]
2026-06-10 16:16 ` [PATCH net 2/8] netfilter: nf_tables_offload: drop device refcount on error Pablo Neira Ayuso
2026-06-10 16:16 ` [PATCH net 3/8] netfilter: nf_conntrack: destroy stale expectfn expectations on unregister Pablo Neira Ayuso
2026-06-10 16:16 ` [PATCH net 4/8] netfilter: x_tables: avoid leaking percpu counter pointers Pablo Neira Ayuso
2026-06-10 16:16 ` [PATCH net 5/8] netfilter: nf_log: validate MAC header was set before dumping it Pablo Neira Ayuso
2026-06-10 16:16 ` [PATCH net 6/8] netfilter: nft_exthdr: fix register tracking for F_PRESENT flag Pablo Neira Ayuso
2026-06-10 16:16 ` [PATCH net 7/8] netfilter: nft_fib: fix stale stack leak via the OIFNAME register Pablo Neira Ayuso
2026-06-10 16:16 ` [PATCH net 8/8] netfilter: nft_meta_bridge: fix stale stack leak via IIFHWADDR register 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=178117441489.3886909.15763136255322020254.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=fw@strlen.de \
--cc=horms@kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox