Re: [PATCH bpf-next v1 1/2] bpf: Disable file_alloc_security hook

[patchwork-bot+netdevbpf@kernel.org]

Hello:

This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:

On Wed, 26 Nov 2025 12:29:26 -0800 you wrote:
> A use-after-free bug may be triggered by calling bpf_inode_storage_get()
> in a BPF LSM program hooked to file_alloc_security. Disable the hook to
> prevent this from happening.
> 
> The cause of the bug is shown in the trace below. In alloc_file(), a
> file struct is first allocated through kmem_cache_alloc(). Then,
> file_alloc_security hook is invoked. Since the zero initialization or
> assignment of f->f_inode happen after this LSM hook, a BPF program may
> get a dangeld inode pointer by walking the file struct.
> 
> [...]

Here is the summary with links:
  - [bpf-next,v1,1/2] bpf: Disable file_alloc_security hook
    https://git.kernel.org/bpf/bpf-next/c/b4bf1d23dc1d
  - [bpf-next,v1,2/2] selftests/bpf: Remove usage of lsm/file_alloc_security in selftest
    https://git.kernel.org/bpf/bpf-next/c/a3a60cc120d6

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html