From: patchwork-bot+netdevbpf@kernel.org
To: YiFei Zhu <zhuyifei@google.com>
Cc: bpf@vger.kernel.org, alexei.starovoitov@gmail.com,
jinghao7@illinois.edu, daniel@iogearbox.net, ast@kernel.org,
andrii@kernel.org, song@kernel.org, sdf@google.com,
jdz@google.com, jannh@google.com, mvle@us.ibm.com,
zohar@linux.ibm.com, tyxu.uiuc@gmail.com, security@kernel.org
Subject: Re: [PATCH bpf 1/2] bpf: Restrict bpf_sys_bpf to CAP_PERFMON
Date: Wed, 17 Aug 2022 22:30:14 +0000 [thread overview]
Message-ID: <166077541474.7079.5119695287194972054.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220816205517.682470-1-zhuyifei@google.com>
Hello:
This series was applied to bpf/bpf.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:
On Tue, 16 Aug 2022 20:55:16 +0000 you wrote:
> The verifier cannot perform sufficient validation of any pointers
> passed into bpf_attr and treats them as integers rather than pointers.
> The helper will then read from arbitrary pointers passed into it.
> Restrict the helper to CAP_PERFMON since the security model in
> BPF of arbitrary kernel read is CAP_BPF + CAP_PERFMON.
>
> Fixes: af2ac3e13e45 ("bpf: Prepare bpf syscall to be used from kernel and user space.")
> Signed-off-by: YiFei Zhu <zhuyifei@google.com>
>
> [...]
Here is the summary with links:
- [bpf,1/2] bpf: Restrict bpf_sys_bpf to CAP_PERFMON
https://git.kernel.org/bpf/bpf/c/14b20b784f59
- [bpf,2/2] bpf: Add WARN_ON for recursive prog_run invocation
(no matching commit)
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:[~2022-08-17 22:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-16 20:55 [PATCH bpf 1/2] bpf: Restrict bpf_sys_bpf to CAP_PERFMON YiFei Zhu
2022-08-16 20:55 ` [PATCH bpf 2/2] bpf: Add WARN_ON for recursive prog_run invocation YiFei Zhu
2022-08-17 22:30 ` Daniel Borkmann
2022-08-17 23:20 ` YiFei Zhu
2022-08-17 22:30 ` 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=166077541474.7079.5119695287194972054.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alexei.starovoitov@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=jannh@google.com \
--cc=jdz@google.com \
--cc=jinghao7@illinois.edu \
--cc=mvle@us.ibm.com \
--cc=sdf@google.com \
--cc=security@kernel.org \
--cc=song@kernel.org \
--cc=tyxu.uiuc@gmail.com \
--cc=zhuyifei@google.com \
--cc=zohar@linux.ibm.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;
as well as URLs for NNTP newsgroup(s).