From: Eduard Zingerman <eddyz87@gmail.com>
To: Daniel Borkmann <daniel@iogearbox.net>,
bpf@vger.kernel.org, ast@kernel.org, andrii@kernel.org
Cc: martin.lau@linux.dev, kernel-team@fb.com,
yonghong.song@linux.dev, Chris Mason <clm@meta.com>
Subject: Re: [PATCH bpf] bpf: potential double-free of env->insn_aux_data
Date: Mon, 15 Sep 2025 11:21:49 -0700 [thread overview]
Message-ID: <f8337cf1b17b9bf2ee31ebbb5f79ab7290ca4263.camel@gmail.com> (raw)
In-Reply-To: <fdc291d2-ec13-4a54-9fad-bc905edf4ff8@iogearbox.net>
On Mon, 2025-09-15 at 13:42 +0200, Daniel Borkmann wrote:
[...]
> > diff --git a/kernel/bpf/verifier.c b/kernel/bpf/verifier.c
> > index 9fb1f957a09374e4d148402572b872bec930f34c..92eb0f4e87a4ec3a7e303c6949cb415e3fd0b4ac 100644
> > --- a/kernel/bpf/verifier.c
> > +++ b/kernel/bpf/verifier.c
> > @@ -20781,7 +20781,6 @@ static struct bpf_prog *bpf_patch_insn_data(struct bpf_verifier_env *env, u32 of
> > verbose(env,
> > "insn %d cannot be patched due to 16-bit range\n",
> > env->insn_aux_data[off].orig_idx);
> > - vfree(new_data);
>
> I presume you mean bpf-next tree, otherwise we'd be adding a memory leak into bpf tree?
Hi Daniel,
Yes, the tag should be bpf-next.
Will resend with the correct tag.
I apologize, this was sloppy on my side.
[...]
next prev parent reply other threads:[~2025-09-15 18:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-12 19:18 [PATCH bpf] bpf: potential double-free of env->insn_aux_data Eduard Zingerman
2025-09-15 11:42 ` Daniel Borkmann
2025-09-15 18:21 ` Eduard Zingerman [this message]
2025-09-15 19:28 ` Alexei Starovoitov
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=f8337cf1b17b9bf2ee31ebbb5f79ab7290ca4263.camel@gmail.com \
--to=eddyz87@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=clm@meta.com \
--cc=daniel@iogearbox.net \
--cc=kernel-team@fb.com \
--cc=martin.lau@linux.dev \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.