From: patchwork-bot+netdevbpf@kernel.org
To: Cong Wang <xiyou.wangcong@gmail.com>
Cc: netdev@vger.kernel.org, bpf@vger.kernel.org,
cong.wang@bytedance.com,
syzbot+1989ee16d94720836244@syzkaller.appspotmail.com,
andrii@kernel.org
Subject: Re: [Patch bpf] bpf: fix a potential use-after-free in bpf_link_free()
Date: Tue, 04 Jun 2024 15:50:28 +0000 [thread overview]
Message-ID: <171751622858.21059.9816190030253972766.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240602182703.207276-1-xiyou.wangcong@gmail.com>
Hello:
This patch was applied to bpf/bpf.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:
On Sun, 2 Jun 2024 11:27:03 -0700 you wrote:
> From: Cong Wang <cong.wang@bytedance.com>
>
> After commit 1a80dbcb2dba, bpf_link can be freed by
> link->ops->dealloc_deferred, but the code still tests and uses
> link->ops->dealloc afterward, which leads to a use-after-free as
> reported by syzbot. Actually, one of them should be sufficient, so
> just call one of them instead of both. Also add a WARN_ON() in case
> of any problematic implementation.
>
> [...]
Here is the summary with links:
- [bpf] bpf: fix a potential use-after-free in bpf_link_free()
https://git.kernel.org/bpf/bpf/c/2884dc7d08d9
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-06-04 15:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-02 18:27 [Patch bpf] bpf: fix a potential use-after-free in bpf_link_free() Cong Wang
2024-06-02 19:32 ` Jiri Olsa
2024-06-03 16:15 ` Daniel Borkmann
2024-06-04 15:22 ` Cong Wang
2024-06-04 15: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=171751622858.21059.9816190030253972766.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=cong.wang@bytedance.com \
--cc=netdev@vger.kernel.org \
--cc=syzbot+1989ee16d94720836244@syzkaller.appspotmail.com \
--cc=xiyou.wangcong@gmail.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