netdev - Re: [Patch bpf] bpf: fix a potential use-after-free in bpf_link

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: 
 <171751622858.21059.9816190030253972766.git-patchwork-notify@kernel.org>
Date: Tue, 04 Jun 2024 15:50:28 +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+1989ee16d94720836244@...kaller.appspotmail.com, andrii@...nel.org
Subject: Re: [Patch bpf] bpf: fix a potential use-after-free in bpf_link_free()

Hello:

This patch was applied to bpf/bpf.git (master)
by Daniel Borkmann <daniel@...earbox.net>:

On Sun,  2 Jun 2024 11:27:03 -0700 you wrote:
> From: Cong Wang <cong.wang@...edance.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