From: Andrii Nakryiko <andrii.nakryiko@gmail.com>
To: Jiri Olsa <jolsa@kernel.org>
Cc: Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Andrii Nakryiko <andrii@kernel.org>,
syzbot+a9ed3d9132939852d0df@syzkaller.appspotmail.com,
bpf@vger.kernel.org, linux-perf-users@vger.kernel.org,
Martin KaFai Lau <kafai@fb.com>,
Eduard Zingerman <eddyz87@gmail.com>,
Song Liu <songliubraving@fb.com>, Yonghong Song <yhs@fb.com>,
John Fastabend <john.fastabend@gmail.com>,
Hao Luo <haoluo@google.com>
Subject: Re: [PATCH bpf] bpf: Check the helper function is valid in get_helper_proto
Date: Tue, 12 Aug 2025 15:32:40 -0700 [thread overview]
Message-ID: <CAEf4BzZBe1BkjJDc858W7rv-Eewk+SAoYKGH3qJYO0DP2H3NBQ@mail.gmail.com> (raw)
In-Reply-To: <20250812221220.581452-1-jolsa@kernel.org>
On Tue, Aug 12, 2025 at 3:12 PM Jiri Olsa <jolsa@kernel.org> wrote:
>
> From: Jiri Olsa <olsajiri@gmail.com>
>
> syzbot reported an verifier bug [1] where the helper func pointer
> could be NULL due to disabled config option.
>
> As Alexei suggested we could check on that in get_helper_proto
> directly. Excluding tail_call helper from the check, because it
> is NULL by design and valid in all configs.
>
> [1] https://lore.kernel.org/bpf/68904050.050a0220.7f033.0001.GAE@google.com/
> Reported-by: syzbot+a9ed3d9132939852d0df@syzkaller.appspotmail.com
> Suggested-by: Alexei Starovoitov <ast@kernel.org>
> Signed-off-by: Jiri Olsa <jolsa@kernel.org>
> ---
> kernel/bpf/verifier.c | 9 ++++++++-
> 1 file changed, 8 insertions(+), 1 deletion(-)
>
> diff --git a/kernel/bpf/verifier.c b/kernel/bpf/verifier.c
> index c4f69a9e9af6..5e38489656e2 100644
> --- a/kernel/bpf/verifier.c
> +++ b/kernel/bpf/verifier.c
> @@ -11344,6 +11344,13 @@ static bool can_elide_value_nullness(enum bpf_map_type type)
> }
> }
>
> +static bool is_valid_proto(const struct bpf_func_proto *fn)
> +{
> + if (fn == &bpf_tail_call_proto)
> + return true;
ugh... what if we set bpf_tail_call_proto's .func to (void *)0xDEADBAD
or some such and avoid this special casing?
> + return fn && fn->func;
> +}
> +
> static int get_helper_proto(struct bpf_verifier_env *env, int func_id,
> const struct bpf_func_proto **ptr)
> {
> @@ -11354,7 +11361,7 @@ static int get_helper_proto(struct bpf_verifier_env *env, int func_id,
> return -EINVAL;
>
> *ptr = env->ops->get_func_proto(func_id, env->prog);
> - return *ptr ? 0 : -EINVAL;
so we explicitly do not want WARN/BUG/verifier_bug() if
!is_valid_proto(), is that right?
> + return is_valid_proto(*ptr) ? 0 : -EINVAL;
> }
>
> static int check_helper_call(struct bpf_verifier_env *env, struct bpf_insn *insn,
> --
> 2.50.1
>
next prev parent reply other threads:[~2025-08-12 22:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-12 22:12 [PATCH bpf] bpf: Check the helper function is valid in get_helper_proto Jiri Olsa
2025-08-12 22:32 ` Andrii Nakryiko [this message]
2025-08-13 8:27 ` Jiri Olsa
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=CAEf4BzZBe1BkjJDc858W7rv-Eewk+SAoYKGH3qJYO0DP2H3NBQ@mail.gmail.com \
--to=andrii.nakryiko@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kafai@fb.com \
--cc=linux-perf-users@vger.kernel.org \
--cc=songliubraving@fb.com \
--cc=syzbot+a9ed3d9132939852d0df@syzkaller.appspotmail.com \
--cc=yhs@fb.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).