linux-kernel - Re: [PATCH v7 bpf-next 0/2] security: Propagate caller information in bpf hooks

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 for Android: free password hash cracker in your pocket

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

Message-Id: 
 <174169323352.3916299.12862779814238590345.git-patchwork-notify@kernel.org>
Date: Tue, 11 Mar 2025 11:40:33 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Blaise Boscaccy <bboscaccy@...ux.microsoft.com>
Cc: paul@...l-moore.com, jmorris@...ei.org, serge@...lyn.com, ast@...nel.org,
 daniel@...earbox.net, john.fastabend@...il.com, andrii@...nel.org,
 martin.lau@...ux.dev, eddyz87@...il.com, song@...nel.org,
 yonghong.song@...ux.dev, kpsingh@...nel.org, sdf@...ichev.me,
 haoluo@...gle.com, jolsa@...nel.org, stephen.smalley.work@...il.com,
 omosnace@...hat.com, mykolal@...com, shuah@...nel.org, memxor@...il.com,
 mattbobrowski@...gle.com, xukuohai@...wei.com, linux-kernel@...r.kernel.org,
 linux-security-module@...r.kernel.org, bpf@...r.kernel.org,
 selinux@...r.kernel.org, linux-kselftest@...r.kernel.org
Subject: Re: [PATCH v7 bpf-next 0/2] security: Propagate caller information in bpf
 hooks

Hello:

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

On Mon, 10 Mar 2025 15:17:10 -0700 you wrote:
> Hello,
> 
> While trying to implement an eBPF gatekeeper program, we ran into an
> issue whereas the LSM hooks are missing some relevant data.
> 
> Certain subcommands passed to the bpf() syscall can be invoked from
> either the kernel or userspace. Additionally, some fields in the
> bpf_attr struct contain pointers, and depending on where the
> subcommand was invoked, they could point to either user or kernel
> memory. One example of this is the bpf_prog_load subcommand and its
> fd_array. This data is made available and used by the verifier but not
> made available to the LSM subsystem. This patchset simply exposes that
> information to applicable LSM hooks.
> 
> [...]

Here is the summary with links:
  - [v7,bpf-next,1/2] security: Propagate caller information in bpf hooks
    https://git.kernel.org/bpf/bpf-next/c/a8cd03532fc9
  - [v7,bpf-next,2/2] selftests/bpf: Add a kernel flag test for LSM bpf hook
    https://git.kernel.org/bpf/bpf-next/c/f563314d7293

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