From: Yonghong Song <yonghong.song@linux.dev>
To: Xu Kuohai <xukuohai@huaweicloud.com>,
bpf@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Andrii Nakryiko <andrii@kernel.org>,
Martin KaFai Lau <martin.lau@linux.dev>,
Eduard Zingerman <eddyz87@gmail.com>,
Kumar Kartikeya Dwivedi <memxor@gmail.com>,
Stanislav Fomichev <sdf@fomichev.me>,
YiFei Zhu <zhuyifei@google.com>,
Matt Bobrowski <mattbobrowski@google.com>,
Quan Sun <2022090917019@std.uestc.edu.cn>
Subject: Re: [PATCH bpf v4 2/3] bpf: Add validation for bpf_set_retval argument
Date: Thu, 4 Jun 2026 12:19:41 -0700 [thread overview]
Message-ID: <c7d73755-cc38-4dc0-9d8a-058fc6243d2e@linux.dev> (raw)
In-Reply-To: <20260604130458.617765-3-xukuohai@huaweicloud.com>
On 6/4/26 6:04 AM, Xu Kuohai wrote:
> From: Xu Kuohai <xukuohai@huawei.com>
>
> The bpf_set_retval() helper is used by cgroup BPF programs to set the
> return value of the target hook. The argument type for this helper is
> ARG_ANYTHING. This allows setting a positive value, which no cgroup
> hook expects and can cause issues, such as:
>
> - BPF_LSM_CGROUP: a positive value from bpf_lsm_socket_create bypasses
> the err < 0 check in __sock_create(), leaving the socket object
> unallocated. The positive return value is then propagated to the
> syscall entry __sys_socket(), which also bypasses the IS_ERR() guard
> and ultimately causes a NULL pointer dereference.
>
> - BPF_CGROUP_DEVICE: a positive value can be returned through cgroup
> device bpf prog -> devcgroup_check_permission() -> bdev_permission()
> -> bdev_file_open_by_dev(), where ERR_PTR(positive) produces a pointer
> that IS_ERR() does not catch, leading to a wild pointer dereference.
>
> - BPF_CGROUP_SOCK: a positive value can be returned through cgroup sock
> bpf prog -> __cgroup_bpf_run_filter_sk() -> inet_create() ->
> __sock_create(), where inet_create() frees the newly allocated sk
> via sk_common_release() and sets sock->sk = NULL on the non-zero
> return, but __sock_create() only checks err < 0 for cleanup, so a
> positive retval bypasses cleanup and returns a socket with NULL sk
> to userspace, triggering a NULL pointer dereference on subsequent
> socket operations.
>
> - BPF_CGROUP_SYSCTL: a positive value can be returned through the cgroup
> bpf prog -> __cgroup_bpf_run_filter_sysctl() -> proc_sys_call_handler(),
> where a non-zero return bypasses the normal sysctl proc_handler and is
> returned directly to userspace as return value of read() or write()
> syscall.
FYI, the following patch:
https://lore.kernel.org/bpf/20260603105317.944304-4-dawei.feng@seu.edu.cn/
will change return value for BPF_CGROUP_SYSCTL from 1 to 0.
>
> So add validation for the argument of the bpf_set_retval() helper.
>
> For BPF_LSM_CGROUP, enforce the LSM hook specific range returned by
> bpf_lsm_get_retval_range().
>
> For all other cgroup program types, restrict the argument to
> [-MAX_ERRNO, 0], which matches the kernel convention of 0 for success
> and negative errno for error.
>
> BPF_CGROUP_GETSOCKOPT is an exception, since valid getsockopt
> implementations may return positive values, as allowed by commit
> c4dcfdd406aa ("bpf: Move getsockopt retval to struct bpf_cg_run_ctx").
>
> Also refine the return value range of bpf_get_retval() so that
> values returned by bpf_get_retval() can be passed directly to
> bpf_set_retval() without extra manual bounds checking.
>
> Fixes: b44123b4a3dc ("bpf: Add cgroup helpers bpf_{get,set}_retval to get/set syscall return value")
> Fixes: 69fd337a975c ("bpf: per-cgroup lsm flavor")
> Reported-by: Quan Sun <2022090917019@std.uestc.edu.cn>
> Closes: https://lore.kernel.org/all/567d3206-74a5-44e5-99c6-779c425f399e@std.uestc.edu.cn
> Signed-off-by: Xu Kuohai <xukuohai@huawei.com>
> ---
> kernel/bpf/verifier.c | 54 +++++++++++++++++++++++++++++++++++++++++++
> 1 file changed, 54 insertions(+)
>
[...]
next prev parent reply other threads:[~2026-06-04 19:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-04 13:04 [PATCH bpf v4 0/3] Add validation for bpf_set_retval helper Xu Kuohai
2026-06-04 13:04 ` [PATCH bpf v4 1/3] selftests/bpf: Restrict bpf_set_retval argument in sk_bypass_prot_mem Xu Kuohai
2026-06-04 13:04 ` [PATCH bpf v4 2/3] bpf: Add validation for bpf_set_retval argument Xu Kuohai
2026-06-04 13:52 ` bot+bpf-ci
2026-06-04 16:29 ` Alexei Starovoitov
2026-06-05 2:49 ` Xu Kuohai
2026-06-04 19:19 ` Yonghong Song [this message]
2026-06-05 2:51 ` Xu Kuohai
2026-06-04 13:04 ` [PATCH bpf v4 3/3] selftests/bpf: Add tests for bpf_set_retval validation Xu Kuohai
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=c7d73755-cc38-4dc0-9d8a-058fc6243d2e@linux.dev \
--to=yonghong.song@linux.dev \
--cc=2022090917019@std.uestc.edu.cn \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=mattbobrowski@google.com \
--cc=memxor@gmail.com \
--cc=sdf@fomichev.me \
--cc=xukuohai@huaweicloud.com \
--cc=zhuyifei@google.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
Powered by JetHome