From: patchwork-bot+netdevbpf@kernel.org
To: Junseo Lim <zirajs7@gmail.com>
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
eddyz87@gmail.com, memxor@gmail.com, martin.lau@linux.dev,
sdf@fomichev.me, song@kernel.org, yonghong.song@linux.dev,
jolsa@kernel.org, emil@etsalapatis.com, bpf@vger.kernel.org,
linux-kernel@vger.kernel.org, rhkrqnwk98@gmail.com
Subject: Re: [PATCH bpf v2 0/2] bpf: Reject negative optlen in cgroup getsockopt hook
Date: Mon, 17 Aug 2026 09:50:07 +0000 [thread overview]
Message-ID: <178696020739.1047534.3951933136786792330.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1786448307.git.zirajs7@gmail.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:
On Tue, 11 Aug 2026 23:19:06 +0900 you wrote:
> A cgroup getsockopt BPF program can set a negative optlen after the
> kernel getsockopt handler has run. For TCP_ZEROCOPY_RECEIVE, the
> kernel-buffer hook did not validate the lower bound and the negative
> value could reach copy_to_sockptr() as a size_t.
>
> Patch 1 rejects negative optlen values in the kernel-buffer hook.
> Patch 2 adds a test_progs selftest that reproduces the issue through
> TCP_ZEROCOPY_RECEIVE.
>
> [...]
Here is the summary with links:
- [bpf,v2,1/2] bpf: Reject negative optlen in cgroup getsockopt hook
https://git.kernel.org/bpf/bpf-next/c/1b5aacd5b241
- [bpf,v2,2/2] selftests/bpf: Exercise negative optlen in cgroup getsockopt hook
https://git.kernel.org/bpf/bpf-next/c/6b0835ac79b2
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:[~2026-08-17 9:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-11 14:19 [PATCH bpf v2 0/2] bpf: Reject negative optlen in cgroup getsockopt hook Junseo Lim
2026-08-11 14:19 ` [PATCH bpf v2 1/2] " Junseo Lim
2026-08-11 14:19 ` [PATCH bpf v2 2/2] selftests/bpf: Exercise " Junseo Lim
2026-08-11 15:10 ` bot+bpf-ci
2026-08-17 4:57 ` Junseo Lim
2026-08-17 9:50 ` 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=178696020739.1047534.3951933136786792330.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=emil@etsalapatis.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=memxor@gmail.com \
--cc=rhkrqnwk98@gmail.com \
--cc=sdf@fomichev.me \
--cc=song@kernel.org \
--cc=yonghong.song@linux.dev \
--cc=zirajs7@gmail.com \
/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.