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,
Michal Hocko <mhocko@suse.com>
Subject: Re: CVE-2023-52793: samples/bpf: syscall_tp_user: Fix array out-of-bound access
Date: Fri, 24 May 2024 06:36:19 +0200 [thread overview]
Message-ID: <2024052404-founding-motion-5e89@gregkh> (raw)
In-Reply-To: <7p643u2dcn6cen32dbtrcki62qrn3o2hyiplbx2hkpcojuiev5@3hbnkswhtha3>
On Fri, May 24, 2024 at 11:58:54AM +0800, Shung-Hsi Yu wrote:
> On Tue, 21 May 2024 17:31:29 +0200, Greg Kroah-Hartman wrote:
> > Description
> > ===========
> >
> > In the Linux kernel, the following vulnerability has been resolved:
> >
> > samples/bpf: syscall_tp_user: Fix array out-of-bound access
> >
> > Commit 06744f24696e ("samples/bpf: Add openat2() enter/exit tracepoint
> > to syscall_tp sample") added two more eBPF programs to support the
> > openat2() syscall. However, it did not increase the size of the array
> > that holds the corresponding bpf_links. This leads to an out-of-bound
> > access on that array in the bpf_object__for_each_program loop and could
> > corrupt other variables on the stack. On our testing QEMU, it corrupts
> > the map1_fds array and causes the sample to fail:
> >
> > # ./syscall_tp
> > prog #0: map ids 4 5
> > verify map:4 val: 5
> > map_lookup failed: Bad file descriptor
> >
> > Dynamically allocate the array based on the number of programs reported
> > by libbpf to prevent similar inconsistencies in the future
> >
> > The Linux kernel CVE team has assigned CVE-2023-52793 to this issue.
>
> I would like to dispute this CVE.
>
> Files in samples/bpf are meant to serve as an example and not code that
> are directly used at run-time, hence I believe this bug does not have
> security implication.
You are right, sorry about that, now rejected. Thanks for the review!
greg k-h
next prev parent reply other threads:[~2024-05-24 4:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-24 3:58 CVE-2023-52793: samples/bpf: syscall_tp_user: Fix array out-of-bound access Shung-Hsi Yu
2024-05-24 4:36 ` Greg Kroah-Hartman [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-05-21 15:31 Greg Kroah-Hartman
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=2024052404-founding-motion-5e89@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhocko@suse.com \
--cc=shung-hsi.yu@suse.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.