[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <161824200925.5298.15006225388105379863.git-patchwork-notify@kernel.org>
Date: Mon, 12 Apr 2021 15:40:09 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Cong Wang <xiyou.wangcong@...il.com>
Cc: netdev@...r.kernel.org, bpf@...r.kernel.org,
cong.wang@...edance.com,
syzbot+7b6548ae483d6f4c64ae@...kaller.appspotmail.com,
john.fastabend@...il.com, daniel@...earbox.net,
jakub@...udflare.com, lmb@...udflare.com
Subject: Re: [Patch bpf-next] sock_map: fix a potential use-after-free in
sock_map_close()
Hello:
This patch was applied to bpf/bpf-next.git (refs/heads/master):
On Wed, 7 Apr 2021 20:05:56 -0700 you wrote:
> From: Cong Wang <cong.wang@...edance.com>
>
> The last refcnt of the psock can be gone right after
> sock_map_remove_links(), so sk_psock_stop() could trigger a UAF.
> The reason why I placed sk_psock_stop() there is to avoid RCU read
> critical section, and more importantly, some callee of
> sock_map_remove_links() is supposed to be called with RCU read lock,
> we can not simply get rid of RCU read lock here. Therefore, the only
> choice we have is to grab an additional refcnt with sk_psock_get()
> and put it back after sk_psock_stop().
>
> [...]
Here is the summary with links:
- [bpf-next] sock_map: fix a potential use-after-free in sock_map_close()
https://git.kernel.org/bpf/bpf-next/c/aadb2bb83ff7
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
Powered by blists - more mailing lists