From: patchwork-bot+netdevbpf@kernel.org
To: Nandakumar Edamana <nandakumar@nandakumar.co.in>
Cc: bpf@vger.kernel.org, andrii.nakryiko@gmail.com, eddyz87@gmail.com
Subject: Re: [PATCH bpf-next] libbpf: Fix out-of-bound read
Date: Mon, 24 Feb 2025 22:10:41 +0000 [thread overview]
Message-ID: <174043504102.3625999.5963189772004385991.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250221210110.3182084-1-nandakumar@nandakumar.co.in>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:
On Sat, 22 Feb 2025 02:31:11 +0530 you wrote:
> In `set_kcfg_value_str`, an untrusted string is accessed with the assumption
> that it will be at least two characters long due to the presence of checks for
> opening and closing quotes. But the check for the closing quote
> (value[len - 1] != '"') misses the fact that it could be checking the opening
> quote itself in case of an invalid input that consists of just the opening
> quote.
>
> [...]
Here is the summary with links:
- [bpf-next] libbpf: Fix out-of-bound read
https://git.kernel.org/bpf/bpf-next/c/236d3910117e
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2025-02-24 22:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-19 15:13 Out-of-bound read suspected in libbpf.c Nandakumar Edamana
2025-02-20 21:20 ` Eduard Zingerman
2025-02-21 0:41 ` [PATCH] fix: out-of-bound read " Nandakumar Edamana
2025-02-21 18:31 ` Andrii Nakryiko
2025-02-21 21:01 ` [PATCH bpf-next] libbpf: Fix out-of-bound read Nandakumar Edamana
2025-02-24 22:10 ` patchwork-bot+netdevbpf [this message]
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=174043504102.3625999.5963189772004385991.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii.nakryiko@gmail.com \
--cc=bpf@vger.kernel.org \
--cc=eddyz87@gmail.com \
--cc=nandakumar@nandakumar.co.in \
/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.