From: Leon Hwang <leon.hwang@linux.dev>
To: Sanghyun Park <sanghyun.park.cnu@gmail.com>,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Andrii Nakryiko <andrii@kernel.org>,
Eduard Zingerman <eddyz87@gmail.com>,
Kumar Kartikeya Dwivedi <memxor@gmail.com>,
bpf@vger.kernel.org
Cc: John Fastabend <john.fastabend@gmail.com>,
Martin KaFai Lau <martin.lau@linux.dev>,
Song Liu <song@kernel.org>,
Yonghong Song <yonghong.song@linux.dev>,
Jiri Olsa <jolsa@kernel.org>,
Emil Tsalapatis <emil@etsalapatis.com>,
Ihor Solodrai <ihor.solodrai@linux.dev>,
Shuah Khan <shuah@kernel.org>,
Stanislav Fomichev <sdf@fomichev.me>,
Pu Lehui <pulehui@huawei.com>,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org
Subject: Re: [PATCH bpf-next v4 1/2] bpf: Validate program attach type during link update
Date: Mon, 31 Aug 2026 22:48:29 +0800 [thread overview]
Message-ID: <61e8bf2e-b2aa-4f41-9861-1b075cdc8d16@linux.dev> (raw)
In-Reply-To: <20260831023918.1857658-1-sanghyun.park.cnu@gmail.com>
On 2026/8/31 10:39, Sanghyun Park wrote:
> Cgroup link updates compare only the program type. Programs verified
> for different hooks can share a type, so a UDP6 sock_addr program can
> replace a UDP4 program and write beyond the four-byte ipc.addr field in
> the stack-local struct ipcm_cookie. The same gap permits incompatible
> LSM_MAC and LSM_CGROUP replacements.
>
> Validate every replacement program against the link attach type before
> dispatching to the link-specific update operation. Keep the CGROUP_SKB
> CAP_NET_ADMIN check at initial attach so pinned or delegated link FDs can
> still be updated after a capability drop.
>
> Fixes: 0c991ebc8c69 ("bpf: Implement bpf_prog replacement for an active bpf_cgroup_link")
> Signed-off-by: Sanghyun Park <sanghyun.park.cnu@gmail.com>
One nit below, others lgtm:
Acked-by: Leon Hwang <leon.hwang@linux.dev>
> ---
> v4:
> - Validate every program link update through the shared attach-type helper.
> - Fold the LSM attach-flavor check into that helper.
> - Keep the CGROUP_SKB permission check in the attach-only wrapper and rename
> the wrapper to describe that role.
> - Follow the preferred BPF multi-line comment style.
> - Add focused regression selftests as patch 2/2.
> v3: https://lore.kernel.org/r/20260821084726.3769957-2-sanghyun.park.cnu@gmail.com
> - Factor the CGROUP_SKB CAP_NET_ADMIN check into an attach-only helper.
> v2: https://lore.kernel.org/r/20260818061021.2551771-2-sanghyun.park.cnu@gmail.com
> - Extend validation from cgroup sock_addr programs to all cgroup program
> types, including exact LSM attach flavors.
> - Preserve legacy CGROUP_SKB ingress/egress replacement compatibility.
> - Keep the CGROUP_SKB CAP_NET_ADMIN check on attach, not link update.
> v1: https://lore.kernel.org/r/20260805052858.2390918-3-sanghyun.park.cnu@gmail.com
> ---
> kernel/bpf/syscall.c | 31 ++++++++++++++++++++++---------
> 1 file changed, 22 insertions(+), 9 deletions(-)
>
> diff --git a/kernel/bpf/syscall.c b/kernel/bpf/syscall.c
> index 6874ba1424af..84823149dffa 100644
> --- a/kernel/bpf/syscall.c
> +++ b/kernel/bpf/syscall.c
> @@ -4481,14 +4481,9 @@ static int bpf_prog_attach_check_attach_type(const struct bpf_prog *prog,
> case BPF_PROG_TYPE_CGROUP_SOCK_ADDR:
> case BPF_PROG_TYPE_CGROUP_SOCKOPT:
> case BPF_PROG_TYPE_SK_LOOKUP:
> + case BPF_PROG_TYPE_LSM:
> return attach_type == prog->expected_attach_type ? 0 : -EINVAL;
> case BPF_PROG_TYPE_CGROUP_SKB:
> - if (!bpf_token_capable(prog->aux->token, CAP_NET_ADMIN))
> - /* cg-skb progs can be loaded by unpriv user.
> - * check permissions at attach time.
> - */
> - return -EPERM;
> -
> ptype = attach_type_to_prog_type(attach_type);
> if (prog->type != ptype)
> return -EINVAL;
> @@ -4542,6 +4537,20 @@ static int bpf_prog_attach_check_attach_type(const struct bpf_prog *prog,
> }
> }
>
> +static int bpf_prog_attach_check_perm(const struct bpf_prog *prog,
> + enum bpf_attach_type attach_type)
> +{
> + /*
> + * CGROUP_SKB programs can be loaded by unprivileged users, so check
> + * permissions at attach time.
> + */
> + if (prog->type == BPF_PROG_TYPE_CGROUP_SKB &&
> + !bpf_token_capable(prog->aux->token, CAP_NET_ADMIN))
> + return -EPERM;
> +
> + return bpf_prog_attach_check_attach_type(prog, attach_type);
> +}
> +
> static bool is_cgroup_prog_type(enum bpf_prog_type ptype, enum bpf_attach_type atype,
> bool check_atype)
> {
> @@ -4606,7 +4615,7 @@ static int bpf_prog_attach(const union bpf_attr *attr)
> if (IS_ERR(prog))
> return PTR_ERR(prog);
>
> - if (bpf_prog_attach_check_attach_type(prog, attr->attach_type)) {
> + if (bpf_prog_attach_check_perm(prog, attr->attach_type)) {
> bpf_prog_put(prog);
> return -EINVAL;
> }
> @@ -5805,8 +5814,8 @@ static int link_create(union bpf_attr *attr, bpfptr_t uattr)
> if (IS_ERR(prog))
> return PTR_ERR(prog);
>
> - ret = bpf_prog_attach_check_attach_type(prog,
> - attr->link_create.attach_type);
> + ret = bpf_prog_attach_check_perm(prog,
> + attr->link_create.attach_type);
NIT: fold into one line. 100 chars are allowed per line.
Thanks,
Leon
> if (ret)
> goto out;
>
> @@ -5968,6 +5977,10 @@ static int link_update(union bpf_attr *attr)
> goto out_put_progs;
> }
>
> + ret = bpf_prog_attach_check_attach_type(new_prog, link->attach_type);
> + if (ret)
> + goto out_put_progs;
> +
> if (link->ops->update_prog)
> ret = link->ops->update_prog(link, new_prog, old_prog);
> else
prev parent reply other threads:[~2026-08-31 14:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-31 2:39 [PATCH bpf-next v4 1/2] bpf: Validate program attach type during link update Sanghyun Park
2026-08-31 2:39 ` [PATCH bpf-next v4 2/2] selftests/bpf: Cover attach type checks in " Sanghyun Park
2026-08-31 3:49 ` bot+bpf-ci
2026-08-31 14:50 ` Leon Hwang
2026-08-31 14:48 ` Leon Hwang [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=61e8bf2e-b2aa-4f41-9861-1b075cdc8d16@linux.dev \
--to=leon.hwang@linux.dev \
--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=ihor.solodrai@linux.dev \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=memxor@gmail.com \
--cc=pulehui@huawei.com \
--cc=sanghyun.park.cnu@gmail.com \
--cc=sdf@fomichev.me \
--cc=shuah@kernel.org \
--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