From: Thomas Huth <thuth@redhat.com>
To: "Santiago Ruano Rincón" <santiagorr@riseup.net>,
qemu-devel@nongnu.org, "Alexander Bulekov" <alxndr@bu.edu>,
"Chuhong Yuan" <hslester96@gmail.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Michael Tokarev" <mjt@tls.msk.ru>
Subject: Re: Addressing CVE-2024-3446 in qemu versions shipped in debian bullseye and older
Date: Thu, 2 Jan 2025 08:43:54 +0100 [thread overview]
Message-ID: <5dc130c8-2084-4e6f-86e2-21427f08ab33@redhat.com> (raw)
In-Reply-To: <Z3MrCyX8tVQMPjz7@voleno>
On 31/12/2024 00.21, Santiago Ruano Rincón wrote:
> Hello there,
>
> (Please CC me since I am not subscribed to the QEMU devel list.)
>
> I am working on backporting some CVE fixes to old Debian versions
> (bullseye and previous), and I would like to ask you some help to
> confirm if QEMU in those debian releases is affected by CVE-2024-3446 or
> not. This is QEMU 5.2, 3.1 and 2.8.
>
> On the 7.2 branch, the following four commits are required to fix
> CVE-2024-3446:
> https://gitlab.com/qemu-project/qemu/-/commit/e070e5e6748e3217028fa21aa30bb51f862368c8
> https://gitlab.com/qemu-project/qemu/-/commit/6d37a308159766cb90ed745cfeb1880937b638ec
> https://gitlab.com/qemu-project/qemu/-/commit/e7c2df3fd748a20a8b7a316d186b3ac77551f159
> https://gitlab.com/qemu-project/qemu/-/commit/7aaf5f7778de4d75a169ab193f08857eb28db3a4
>
> AFAICS, the qemu_bh_new calls were replaced with qemu_bh_new_guarded in
> 7.2.6.
>
> Please note that 6d37a308159766cb90ed745cfeb1880937b638ec (and
> ba28e0ff4d95b56dc334aac2730ab3651ffc3132) include this bug as reference:
> https://bugs.launchpad.net/qemu/+bug/1888606. Could you please confirm
> the CVE relates to the same issue?
>
> I am unable to reproduce the issue. I've tried the reproducer found at
> 6d37a308 and the one from the ubuntu referenced bug. However comment #5
> in the ubuntu bug mentions it was reproducible with QEMU 5.0, so I am
> confused.
Hi!
Just to double-check: Did you compile your QEMU with address sanitizer
enabled? Otherwise you might not see the issue when running the reproducer.
Thomas
> To summarise: it OK to affirm QEMU 5.x and older is unaffected by
> CVE-2024-3446?
>
> Thanks in advance, and happy new year!
>
> -- Santiago
next prev parent reply other threads:[~2025-01-02 7:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-30 23:21 Addressing CVE-2024-3446 in qemu versions shipped in debian bullseye and older Santiago Ruano Rincón
2025-01-02 7:43 ` Thomas Huth [this message]
2025-01-08 18:16 ` Santiago Ruano Rincón
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=5dc130c8-2084-4e6f-86e2-21427f08ab33@redhat.com \
--to=thuth@redhat.com \
--cc=alxndr@bu.edu \
--cc=hslester96@gmail.com \
--cc=mjt@tls.msk.ru \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=santiagorr@riseup.net \
/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.