From: Tony Ambardar <tony.ambardar@gmail.com>
To: shivam tiwari <shivam.tiwari00021@gmail.com>
Cc: Andrii Nakryiko <andrii@kernel.org>,
Eduard Zingerman <eddyz87@gmail.com>,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Martin KaFai Lau <martin.lau@linux.dev>,
Song Liu <song@kernel.org>,
Yonghong Song <yonghong.song@linux.dev>,
John Fastabend <john.fastabend@gmail.com>,
KP Singh <kpsingh@kernel.org>,
Stanislav Fomichev <sdf@fomichev.me>, Hao Luo <haoluo@google.com>,
Jiri Olsa <jolsa@kernel.org>,
bpf@vger.kernel.org
Subject: Re: [PATCH bpf v1] libbpf: fix accessing BTF.ext core_relo header
Date: Mon, 27 Jan 2025 18:33:57 -0800 [thread overview]
Message-ID: <Z5hCFR91L7stFn81@kodidev-ubuntu> (raw)
In-Reply-To: <CALz0HOqsN1VqK1WpmNE4jf+AoQ5Frsan7Ysk_R8LhKdRJxV7_Q@mail.gmail.com>
Hi Shivam,
On Sat, Jan 25, 2025 at 01:57:54PM +0530, shivam tiwari wrote:
> Hii Team,
>
> I am new to contributing to the Linux kernel and recently submitted a
> patch via the mailing list. I received a response with a proposed patch
> update and I would like to kindly ask for clarification on the status of my
> submission.
I confess I mistook your email for an automated bug notification from
OSS-Fuzz concerning code I previously contributed, which lead me to
investigate and send out a patch.
Regards,
Tony Ambardar
>
> Does the patch provided represent a draft or suggested change for my
> initial patch? Should I make any modifications or take further actions to
> move this forward? Or has the patch already been accepted for inclusion in
> the project?
>
> I appreciate your time and feedback, and I look forward to your guidance on
> the next steps.
>
> Thank you for your support
>
> On Sat, Jan 25, 2025, 12:22 PM Tony Ambardar <tony.ambardar@gmail.com>
> wrote:
>
> > From: Tony Ambardar <tony.ambardar@gmail.com>
> >
> > Update btf_ext_parse_info() to ensure the core_relo header is present
> > before reading its fields. This avoids a potential buffer read overflow
> > reported by the OSS Fuzz project.
> >
> > Fixes: cf579164e9ea ("libbpf: Support BTF.ext loading and output in either
> > endianness")
> > Link: https://issues.oss-fuzz.com/issues/388905046
> > Signed-off-by: Tony Ambardar <tony.ambardar@gmail.com>
> > ---
> > tools/lib/bpf/btf.c | 4 ++--
> > 1 file changed, 2 insertions(+), 2 deletions(-)
> >
> > diff --git a/tools/lib/bpf/btf.c b/tools/lib/bpf/btf.c
> > index 48c66f3a9200..560b519f820e 100644
> > --- a/tools/lib/bpf/btf.c
> > +++ b/tools/lib/bpf/btf.c
> > @@ -3015,8 +3015,6 @@ static int btf_ext_parse_info(struct btf_ext
> > *btf_ext, bool is_native)
> > .desc = "line_info",
> > };
> > struct btf_ext_sec_info_param core_relo = {
> > - .off = btf_ext->hdr->core_relo_off,
> > - .len = btf_ext->hdr->core_relo_len,
> > .min_rec_size = sizeof(struct bpf_core_relo),
> > .ext_info = &btf_ext->core_relo_info,
> > .desc = "core_relo",
> > @@ -3034,6 +3032,8 @@ static int btf_ext_parse_info(struct btf_ext
> > *btf_ext, bool is_native)
> > if (btf_ext->hdr->hdr_len < offsetofend(struct btf_ext_header,
> > core_relo_len))
> > return 0; /* skip core relos parsing */
> >
> > + core_relo.off = btf_ext->hdr->core_relo_off;
> > + core_relo.len = btf_ext->hdr->core_relo_len;
> > err = btf_ext_parse_sec_info(btf_ext, &core_relo, is_native);
> > if (err)
> > return err;
> > --
> > 2.34.1
> >
> >
next prev parent reply other threads:[~2025-01-28 2:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-24 7:55 Vurnability in libbpf heap buffer attached with solution and Issue link shivam tiwari
2025-01-25 6:52 ` [PATCH bpf v1] libbpf: fix accessing BTF.ext core_relo header Tony Ambardar
2025-01-27 22:30 ` patchwork-bot+netdevbpf
[not found] ` <CALz0HOqsN1VqK1WpmNE4jf+AoQ5Frsan7Ysk_R8LhKdRJxV7_Q@mail.gmail.com>
2025-01-28 2:33 ` Tony Ambardar [this message]
2025-01-27 20:44 ` Vurnability in libbpf heap buffer attached with solution and Issue link Eduard Zingerman
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=Z5hCFR91L7stFn81@kodidev-ubuntu \
--to=tony.ambardar@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=kpsingh@kernel.org \
--cc=martin.lau@linux.dev \
--cc=sdf@fomichev.me \
--cc=shivam.tiwari00021@gmail.com \
--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