From: Michal Hocko <mhocko@suse.com>
To: cve@kernel.org, linux-kernel@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: CVE-2023-52521: bpf: Annotate bpf_long_memcpy with data_race
Date: Tue, 5 Mar 2024 17:54:45 +0100 [thread overview]
Message-ID: <ZedOVc9h_VTBjHLD@tiehlicka> (raw)
In-Reply-To: <2024030253-CVE-2023-52521-d847@gregkh>
On Sat 02-03-24 22:53:05, Greg KH wrote:
> Description
> ===========
>
> In the Linux kernel, the following vulnerability has been resolved:
>
> bpf: Annotate bpf_long_memcpy with data_race
>
> syzbot reported a data race splat between two processes trying to
> update the same BPF map value via syscall on different CPUs:
>
> BUG: KCSAN: data-race in bpf_percpu_array_update / bpf_percpu_array_update
I would like to dispute this CVE. It adds data_race annotation which
doesn't have any impact on the code generation.
--
Michal Hocko
SUSE Labs
next parent reply other threads:[~2024-03-05 16:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2024030253-CVE-2023-52521-d847@gregkh>
2024-03-05 16:54 ` Michal Hocko [this message]
2024-03-05 22:22 ` CVE-2023-52521: bpf: Annotate bpf_long_memcpy with data_race 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=ZedOVc9h_VTBjHLD@tiehlicka \
--to=mhocko@suse.com \
--cc=cve@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
/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