From: patchwork-bot+netdevbpf@kernel.org
To: Tony Ambardar <tony.ambardar@gmail.com>
Cc: shivam.tiwari00021@gmail.com, andrii@kernel.org,
eddyz87@gmail.com, ast@kernel.org, daniel@iogearbox.net,
martin.lau@linux.dev, song@kernel.org, yonghong.song@linux.dev,
john.fastabend@gmail.com, kpsingh@kernel.org, sdf@fomichev.me,
haoluo@google.com, 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 22:30:31 +0000 [thread overview]
Message-ID: <173801703177.3242514.15771856422421899394.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250125065236.2603346-1-itugrok@yahoo.com>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:
On Fri, 24 Jan 2025 22:52:36 -0800 you 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>
>
> [...]
Here is the summary with links:
- [bpf,v1] libbpf: fix accessing BTF.ext core_relo header
https://git.kernel.org/bpf/bpf-next/c/0fc5dddb9409
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2025-01-27 22:30 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 [this message]
[not found] ` <CALz0HOqsN1VqK1WpmNE4jf+AoQ5Frsan7Ysk_R8LhKdRJxV7_Q@mail.gmail.com>
2025-01-28 2:33 ` Tony Ambardar
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=173801703177.3242514.15771856422421899394.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--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=tony.ambardar@gmail.com \
--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