From: patchwork-bot+netdevbpf@kernel.org
To: Nikolay Aleksandrov <razor@blackwall.org>
Cc: netdev@vger.kernel.org, tobias@waldekranz.com, kuba@kernel.org,
roopa@nvidia.com, bridge@lists.linux.dev, edumazet@google.com,
pabeni@redhat.com,
syzbot+fa04eb8a56fd923fc5d8@syzkaller.appspotmail.com
Subject: Re: [PATCH net] net: bridge: mst: fix vlan use-after-free
Date: Wed, 15 May 2024 10:50:29 +0000 [thread overview]
Message-ID: <171577022964.14646.1553082232866025544.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240513110627.770389-1-razor@blackwall.org>
Hello:
This patch was applied to netdev/net.git (main)
by David S. Miller <davem@davemloft.net>:
On Mon, 13 May 2024 14:06:27 +0300 you wrote:
> syzbot reported a suspicious rcu usage[1] in bridge's mst code. While
> fixing it I noticed that nothing prevents a vlan to be freed while
> walking the list from the same path (br forward delay timer). Fix the rcu
> usage and also make sure we are not accessing freed memory by making
> br_mst_vlan_set_state use rcu read lock.
>
> [1]
> WARNING: suspicious RCU usage
> 6.9.0-rc6-syzkaller #0 Not tainted
>
> [...]
Here is the summary with links:
- [net] net: bridge: mst: fix vlan use-after-free
https://git.kernel.org/netdev/net/c/3a7c1661ae13
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:[~2024-05-15 10:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-13 11:06 [PATCH net] net: bridge: mst: fix vlan use-after-free Nikolay Aleksandrov
2024-05-14 10:04 ` Simon Horman
2024-05-15 10:50 ` 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=171577022964.14646.1553082232866025544.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=bridge@lists.linux.dev \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=razor@blackwall.org \
--cc=roopa@nvidia.com \
--cc=syzbot+fa04eb8a56fd923fc5d8@syzkaller.appspotmail.com \
--cc=tobias@waldekranz.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).