From: Eduard Zingerman <eddyz87@gmail.com>
To: Luis Gerhorst <luis.gerhorst@fau.de>,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
John Fastabend <john.fastabend@gmail.com>,
Andrii Nakryiko <andrii@kernel.org>,
Martin KaFai Lau <martin.lau@linux.dev>,
Song Liu <song@kernel.org>,
Yonghong Song <yonghong.song@linux.dev>,
KP Singh <kpsingh@kernel.org>,
Stanislav Fomichev <sdf@fomichev.me>,
Hao Luo <haoluo@google.com>, Jiri Olsa <jolsa@kernel.org>,
bpf@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH bpf-next] bpf: Remove redundant free_verifier_state()/pop_stack()
Date: Wed, 11 Jun 2025 15:36:55 -0700 [thread overview]
Message-ID: <19f50af28e3a90cbd24b2325da8025e47f221739.camel@gmail.com> (raw)
In-Reply-To: <20250611211431.275731-1-luis.gerhorst@fau.de>
On Wed, 2025-06-11 at 23:14 +0200, Luis Gerhorst wrote:
> This patch removes duplicated code.
>
> Eduard points out [1]:
>
> Same cleanup cycles are done in push_stack() and push_async_cb(),
> both functions are only reachable from do_check_common() via
> do_check() -> do_check_insn().
>
> Hence, I think that cur state should not be freed in push_*()
> functions and pop_stack() loop there is not needed.
>
> This would also fix the 'symptom' for [2], but the issue also has a
> simpler fix which was sent separately. This fix also makes sure the
> push_*() callers always return an error for which
> error_recoverable_with_nospec(err) is false. This is required because
> otherwise we try to recover and access the stale `state`.
>
> [1] https://lore.kernel.org/all/b6931bd0dd72327c55287862f821ca6c4c3eb69a.camel@gmail.com/
> [2] https://lore.kernel.org/all/68497853.050a0220.33aa0e.036a.GAE@google.com/
>
> Reported-by: Eduard Zingerman <eddyz87@gmail.com>
> Link: https://lore.kernel.org/all/b6931bd0dd72327c55287862f821ca6c4c3eb69a.camel@gmail.com/
> Signed-off-by: Luis Gerhorst <luis.gerhorst@fau.de>
> ---
Acked-by: Eduard Zingerman <eddyz87@gmail.com>
> kernel/bpf/verifier.c | 26 +++++++++++---------------
> 1 file changed, 11 insertions(+), 15 deletions(-)
>
> diff --git a/kernel/bpf/verifier.c b/kernel/bpf/verifier.c
> index d3bff0385a55..fa147c207c4b 100644
> --- a/kernel/bpf/verifier.c
> +++ b/kernel/bpf/verifier.c
> @@ -2066,10 +2066,10 @@ static struct bpf_verifier_state *push_stack(struct bpf_verifier_env *env,
> }
> return &elem->st;
> err:
> - free_verifier_state(env->cur_state, true);
> - env->cur_state = NULL;
> - /* pop all elements and return */
> - while (!pop_stack(env, NULL, NULL, false));
> + /* free_verifier_state() and pop_stack() loop will be done in
> + * do_check_common(). Caller must return an error for which
> + * error_recoverable_with_nospec(err) is false.
> + */
Nit: I think these comments are unnecessary as same logic applies to many places.
> return NULL;
> }
>
> @@ -2838,10 +2838,10 @@ static struct bpf_verifier_state *push_async_cb(struct bpf_verifier_env *env,
> elem->st.frame[0] = frame;
> return &elem->st;
> err:
> - free_verifier_state(env->cur_state, true);
> - env->cur_state = NULL;
> - /* pop all elements and return */
> - while (!pop_stack(env, NULL, NULL, false));
> + /* free_verifier_state() and pop_stack() loop will be done in
> + * do_check_common(). Caller must return an error for which
> + * error_recoverable_with_nospec(err) is false.
> + */
> return NULL;
> }
>
> @@ -22904,13 +22904,9 @@ static int do_check_common(struct bpf_verifier_env *env, int subprog)
>
> ret = do_check(env);
> out:
> - /* check for NULL is necessary, since cur_state can be freed inside
> - * do_check() under memory pressure.
> - */
> - if (env->cur_state) {
> - free_verifier_state(env->cur_state, true);
> - env->cur_state = NULL;
> - }
> + WARN_ON_ONCE(!env->cur_state);
> + free_verifier_state(env->cur_state, true);
> + env->cur_state = NULL;
> while (!pop_stack(env, NULL, NULL, false));
Nit: while at it, I'd push both free_verifier_state() and pop_stack()
into free_states() a few lines below.
> if (!ret && pop_log)
> bpf_vlog_reset(&env->log, 0);
>
> base-commit: 1d251153a480fc7467d00a8c5dabc55cc6166c43
next prev parent reply other threads:[~2025-06-11 22:36 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-11 12:36 [syzbot] [bpf?] KASAN: slab-use-after-free Read in do_check syzbot
2025-06-11 13:02 ` Eduard Zingerman
2025-06-11 14:03 ` Luis Gerhorst
2025-06-11 17:20 ` Eduard Zingerman
2025-06-11 21:07 ` [PATCH bpf-next] bpf: Fix state use-after-free on push_stack() err Luis Gerhorst
2025-06-11 22:23 ` Eduard Zingerman
2025-06-11 23:10 ` patchwork-bot+netdevbpf
2025-06-11 21:14 ` [PATCH bpf-next] bpf: Remove redundant free_verifier_state()/pop_stack() Luis Gerhorst
2025-06-11 22:36 ` Eduard Zingerman [this message]
2025-06-13 9:01 ` [PATCH bpf-next v2] " Luis Gerhorst
2025-06-13 21:17 ` Eduard Zingerman
2025-06-13 22:06 ` Alexei Starovoitov
2025-06-13 9:07 ` [PATCH bpf-next] " Luis Gerhorst
2025-06-11 21:32 ` [syzbot] [bpf?] KASAN: slab-use-after-free Read in do_check Luis Gerhorst
2025-06-11 21:43 ` Eduard Zingerman
2025-06-11 21:40 ` Eduard Zingerman
2025-06-11 23:00 ` syzbot
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=19f50af28e3a90cbd24b2325da8025e47f221739.camel@gmail.com \
--to=eddyz87@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luis.gerhorst@fau.de \
--cc=martin.lau@linux.dev \
--cc=sdf@fomichev.me \
--cc=song@kernel.org \
--cc=yonghong.song@linux.dev \
/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).