From: Yonghong Song <yonghong.song@linux.dev>
To: bpf@vger.kernel.org
Cc: Alexei Starovoitov <ast@kernel.org>,
Andrii Nakryiko <andrii@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
kernel-team@fb.com, Martin KaFai Lau <martin.lau@kernel.org>
Subject: Re: [PATCH bpf-next v2 1/2] bpf: Validate outgoing stack args when btf_prepare_func_args fails
Date: Fri, 15 May 2026 15:55:37 -0700 [thread overview]
Message-ID: <71e09ab5-c1ed-4ff6-9d90-deaac3ab9e5b@linux.dev> (raw)
In-Reply-To: <20260515014958.1186132-1-yonghong.song@linux.dev>
On 5/15/26 3:49 AM, Yonghong Song wrote:
> btf_prepare_func_args() sets sub->arg_cnt before validating arg types.
> If validation fails (e.g. unsupported pointer type in a static subprog),
> check_outgoing_stack_args() is skipped because btf_check_func_arg_match()
> returns early. For static subprogs, check_func_call() ignores non-EFAULT
> errors and proceeds with the call.
>
> This causes the callee to read stack arg slots that the caller never
> stored or not initialized, potentially dereferencing NULL caller->stack_arg_regs
> or getting no-initialized value.
>
> To fix the issue, when btf_prepare_func_args() fails and the subprog expects
> stack args, call check_outgoing_stack_args() to verify the caller initialized
> the slots. Return -EFAULT on failure so the error is not ignored.
>
> Fixes: 3ab5bd317ee2 ("bpf: Set sub->arg_cnt earlier in btf_prepare_func_args()")
> Signed-off-by: Yonghong Song <yonghong.song@linux.dev>
> ---
> kernel/bpf/verifier.c | 10 ++++++++--
> 1 file changed, 8 insertions(+), 2 deletions(-)
>
> Changelogs:
> v1 -> v2:
> - v1: https://lore.kernel.org/bpf/20260514184827.1619863-1-yonghong.song@linux.dev/
> - Remove Reported-by (Sashiko) and add Fixes tag.
>
> diff --git a/kernel/bpf/verifier.c b/kernel/bpf/verifier.c
> index 76a07f09ab64..8dd79b735a69 100644
> --- a/kernel/bpf/verifier.c
> +++ b/kernel/bpf/verifier.c
> @@ -9118,11 +9118,17 @@ static int btf_check_func_arg_match(struct bpf_verifier_env *env, int subprog,
> struct bpf_func_state *caller = cur_func(env);
> struct bpf_verifier_log *log = &env->log;
> u32 i;
> - int ret;
> + int ret, err;
>
> ret = btf_prepare_func_args(env, subprog);
> - if (ret)
> + if (ret) {
> + if (bpf_in_stack_arg_cnt(sub) > 0) {
> + err = check_outgoing_stack_args(env, caller, sub->arg_cnt);
> + if (err)
> + return err;
> + }
> return ret;
> + }
>
> ret = check_outgoing_stack_args(env, caller, sub->arg_cnt);
> if (ret)
Please ignore this patch set. There are more issues related to stack arguments.
I have consolidated them into v3:
https://lore.kernel.org/bpf/20260515225035.821178-1-yonghong.song@linux.dev/
prev parent reply other threads:[~2026-05-15 22:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-15 1:49 [PATCH bpf-next v2 1/2] bpf: Validate outgoing stack args when btf_prepare_func_args fails Yonghong Song
2026-05-15 1:50 ` [PATCH bpf-next v2 2/2] selftests/bpf: Add test for stack arg read without caller write Yonghong Song
2026-05-15 2:31 ` bot+bpf-ci
2026-05-15 6:31 ` Yonghong Song
2026-05-15 22:55 ` Yonghong Song [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=71e09ab5-c1ed-4ff6-9d90-deaac3ab9e5b@linux.dev \
--to=yonghong.song@linux.dev \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=kernel-team@fb.com \
--cc=martin.lau@kernel.org \
/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