From: patchwork-bot+netdevbpf@kernel.org
To: Jeongjun Park <aha310510@gmail.com>
Cc: wei.liu@kernel.org, paul@xen.org, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
madhuparnabhowmik04@gmail.com, xen-devel@lists.xenproject.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net] net/xen-netback: prevent UAF in xenvif_flush_hash()
Date: Thu, 29 Aug 2024 00:20:39 +0000 [thread overview]
Message-ID: <172489083974.1473828.6183768950292270791.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240822181109.2577354-1-aha310510@gmail.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Fri, 23 Aug 2024 03:11:09 +0900 you wrote:
> During the list_for_each_entry_rcu iteration call of xenvif_flush_hash,
> kfree_rcu does not exist inside the rcu read critical section, so if
> kfree_rcu is called when the rcu grace period ends during the iteration,
> UAF occurs when accessing head->next after the entry becomes free.
>
> Therefore, to solve this, you need to change it to list_for_each_entry_safe.
>
> [...]
Here is the summary with links:
- [net] net/xen-netback: prevent UAF in xenvif_flush_hash()
https://git.kernel.org/netdev/net-next/c/0fa5e94a1811
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-08-29 0:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-22 18:11 [PATCH net] net/xen-netback: prevent UAF in xenvif_flush_hash() Jeongjun Park
2024-08-27 11:19 ` Paolo Abeni
2024-08-27 14:14 ` Jakub Kicinski
2024-08-28 12:52 ` Jeongjun Park
2024-08-29 0:06 ` Jakub Kicinski
2024-08-29 0:20 ` 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=172489083974.1473828.6183768950292270791.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=aha310510@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=madhuparnabhowmik04@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=paul@xen.org \
--cc=wei.liu@kernel.org \
--cc=xen-devel@lists.xenproject.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;
as well as URLs for NNTP newsgroup(s).