From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Shung-Hsi Yu <shung-hsi.yu@suse.com>
Cc: cve@kernel.org, linux-kernel@vger.kernel.org,
bpf@vger.kernel.org, "Stanislav Fomichev" <sdf@google.com>,
"Eduard Zingerman" <eddyz87@gmail.com>,
"Toke Høiland-Jørgensen" <toke@redhat.com>,
"Alexei Starovoitov" <ast@kernel.org>,
"Andrii Nakryiko" <andrii@kernel.org>
Subject: Re: CVE-2024-38564: bpf: Add BPF_PROG_TYPE_CGROUP_SKB attach type enforcement in BPF_LINK_CREATE
Date: Thu, 27 Jun 2024 15:29:20 +0200 [thread overview]
Message-ID: <2024062755-crestless-yam-9f2b@gregkh> (raw)
In-Reply-To: <sgnl2ithdfmum4jlgbqcbhenm2roioypqk2ndmyq4xd2h4svwp@s3dmiiaxh3jf>
On Wed, Jun 26, 2024 at 02:44:31PM +0800, Shung-Hsi Yu wrote:
> On Wed, Jun 19, 2024 at 03:36:13PM GMT, Greg Kroah-Hartman wrote:
> > In the Linux kernel, the following vulnerability has been resolved:
> >
> > bpf: Add BPF_PROG_TYPE_CGROUP_SKB attach type enforcement in BPF_LINK_CREATE
> >
> > bpf_prog_attach uses attach_type_to_prog_type to enforce proper
> > attach type for BPF_PROG_TYPE_CGROUP_SKB. link_create uses
> > bpf_prog_get and relies on bpf_prog_attach_check_attach_type
> > to properly verify prog_type <> attach_type association.
> >
> > Add missing attach_type enforcement for the link_create case.
> > Otherwise, it's currently possible to attach cgroup_skb prog
> > types to other cgroup hooks.
> >
> > The Linux kernel CVE team has assigned CVE-2024-38564 to this issue.
> >
> >
> > Affected and fixed versions
> > ===========================
> >
> > Issue introduced in 5.7 with commit af6eea57437a and fixed in 6.6.33 with commit 6675c541f540
> > Issue introduced in 5.7 with commit af6eea57437a and fixed in 6.8.12 with commit 67929e973f5a
> > Issue introduced in 5.7 with commit af6eea57437a and fixed in 6.9.3 with commit b34bbc766510
> > Issue introduced in 5.7 with commit af6eea57437a and fixed in 6.10-rc1 with commit 543576ec15b1
>
> I'd like to dispute the affected commit for this CVE.
>
> The commit that introduced the issue should instead be commit
> 4a1e7c0c63e02 ("bpf: Support attaching freplace programs to multiple
> attach points") in 5.10.
>
> When link_create() was added in commit af6eea57437a, it uses
> bpf_prog_get_type(attr->link_create.prog_fd, ptype) to resolve struct
> bpf_prog, which effectively does the requried
>
> prog->type == attach_type_to_prog_type(attach_type)
>
> check through bpf_prog_get_ok(), and thus would not allow
> BPF_PROG_TYPE_CGROUP_SKB to be attached to other cgroup hooks.
>
> It is in commit 4a1e7c0c63e02 ("bpf: Support attaching freplace programs
> to multiple attach points") that had bpf_prog_get_type() replaced with
> bpf_prog_get() and lead to the removal of such check, making it possible
> to attach BPF_PROG_TYPE_CGROUP_SKB to other cgroup hooks.
>
> [...]
Thanks for the information, we have now adjusted the vulnerable commit
and pushed out the new json information to cve.org
greg k-h
prev parent reply other threads:[~2024-06-27 13:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2024061955-CVE-2024-38564-b069@gregkh>
2024-06-26 6:44 ` CVE-2024-38564: bpf: Add BPF_PROG_TYPE_CGROUP_SKB attach type enforcement in BPF_LINK_CREATE Shung-Hsi Yu
2024-06-27 13:29 ` Greg Kroah-Hartman [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=2024062755-crestless-yam-9f2b@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=cve@kernel.org \
--cc=eddyz87@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sdf@google.com \
--cc=shung-hsi.yu@suse.com \
--cc=toke@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox