From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: Bug 1863025 <1863025@bugs.launchpad.net>, qemu-devel@nongnu.org
Cc: Michael Tokarev <mjt@tls.msk.ru>,
Mauro Matteo Cascella <mcascell@redhat.com>
Subject: Re: [Bug 1863025] Re: Use-after-free after flush in TCG accelerator
Date: Thu, 31 Aug 2023 15:40:25 +0200 [thread overview]
Message-ID: <cb2807f0-fc7d-fc03-376e-09c3d5f10a7f@linaro.org> (raw)
In-Reply-To: <169348611423.1472917.10027704436078423318.malone@juju-98d295-prod-launchpad-3>
Hi Samuel,
On 31/8/23 14:48, Samuel Henrique wrote:
> CVE-2020-24165 was assigned to this:
> https://nvd.nist.gov/vuln/detail/CVE-2020-24165
>
> I had no involvement in the assignment, posting here for reference only.
>
> ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-24165
QEMU 4.2.0 was released in 2019. The issue you report
has been fixed in commit 886cc68943 ("accel/tcg: fix race
in cpu_exec_step_atomic (bug 1863025)") which is included
in QEMU v5.0, released in April 2020, more than 3 years ago.
What do you expect us to do here? I'm not sure whether assigning
CVE for 3 years old code is a good use of engineering time.
Regards,
Phil.
next prev parent reply other threads:[~2023-08-31 13:40 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-12 22:01 [Bug 1863025] [NEW] Use-after-free after flush in TCG accelerator Yifan
2020-02-14 14:23 ` [Bug 1863025] " Alex Bennée
2020-02-14 14:29 ` Alex Bennée
2020-02-14 14:49 ` [PATCH] accel/tcg: fix race in cpu_exec_step_atomic (bug 1863025) Alex Bennée
2020-02-14 14:49 ` [Bug 1863025] Re: Use-after-free after flush in TCG accelerator Alex Bennée
2020-02-14 15:22 ` [PATCH] accel/tcg: fix race in cpu_exec_step_atomic (bug 1863025) Paolo Bonzini
2020-02-14 23:31 ` Richard Henderson
2020-02-15 0:01 ` Yifan Lu
2020-02-15 0:01 ` [Bug 1863025] " Yifan
2020-02-14 14:51 ` [Bug 1863025] Re: Use-after-free after flush in TCG accelerator Alex Bennée
2020-02-14 18:09 ` Yifan
2020-02-14 18:18 ` Yifan
2020-03-10 9:14 ` Laurent Vivier
2020-04-30 13:43 ` Laurent Vivier
2023-08-31 12:48 ` Samuel Henrique
2023-08-31 13:40 ` Philippe Mathieu-Daudé [this message]
2023-08-31 13:57 ` Daniel P. Berrangé
2023-08-31 13:57 ` Daniel Berrange
2023-08-31 14:10 ` Mauro Matteo Cascella
2023-08-31 14:10 ` Mauro Matteo Cascella
2023-08-31 14:12 ` Mauro Matteo Cascella
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=cb2807f0-fc7d-fc03-376e-09c3d5f10a7f@linaro.org \
--to=philmd@linaro.org \
--cc=1863025@bugs.launchpad.net \
--cc=mcascell@redhat.com \
--cc=mjt@tls.msk.ru \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).