From: patchwork-bot+netdevbpf@kernel.org
To: Ren Wei <enjou1224z@gmail.com>
Cc: bridge@lists.linux.dev, netdev@vger.kernel.org,
razor@blackwall.org, idosch@nvidia.com, davem@davemloft.net,
edumazet@google.com, pabeni@redhat.com, horms@kernel.org,
nbd@nbd.name, linus.luessing@c0d3.blue, vega@nebusec.ai,
zhilinz@nebusec.ai
Subject: Re: [PATCH net 0/1] net: bridge: fix fast-leave use-after-free
Date: Mon, 27 Jul 2026 22:40:20 +0000 [thread overview]
Message-ID: <178519202013.1443317.3670329492058915531.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1784707712.git.zhilinz@nebusec.ai>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Fri, 24 Jul 2026 00:52:47 +0800 you wrote:
> From: Zhiling Zou <zhilinz@nebusec.ai>
>
> Hi Linux kernel maintainers,
>
> We found and validated a issue in net/bridge/br_multicast.c. The bug
> is reachable by a non-root user via user and net namespace.
> We've tested it, and it should not affect any other functionality.
>
> [...]
Here is the summary with links:
- [net,1/1] net: bridge: stop fast-leave after deleting a port group
https://git.kernel.org/netdev/net/c/a39789f211b8
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-07-27 22:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-23 16:52 [PATCH net 0/1] net: bridge: fix fast-leave use-after-free Ren Wei
2026-07-23 16:52 ` [PATCH net 1/1] net: bridge: stop fast-leave after deleting a port group Ren Wei
2026-07-26 10:13 ` Nikolay Aleksandrov
2026-07-27 22:40 ` patchwork-bot+netdevbpf [this message]
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=178519202013.1443317.3670329492058915531.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=bridge@lists.linux.dev \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=enjou1224z@gmail.com \
--cc=horms@kernel.org \
--cc=idosch@nvidia.com \
--cc=linus.luessing@c0d3.blue \
--cc=nbd@nbd.name \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=razor@blackwall.org \
--cc=vega@nebusec.ai \
--cc=zhilinz@nebusec.ai \
/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.