From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: Salvatore Bonaccorso <carnil@debian.org>,
T K Sourabh <sourabhtk37@gmail.com>
Cc: Stefan Hajnoczi <stefanha@gmail.com>,
qemu-devel@nongnu.org, Bin Meng <bin.meng@windriver.com>,
Hanna Reitz <hreitz@redhat.com>,
David Hildenbrand <david@redhat.com>,
Kevin Wolf <kwolf@redhat.com>,
qemu-block@nongnu.org, Peter Xu <peterx@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [PULL 0/3] Memory/SDHCI/ParallelFlash patches for v7.2.0-rc0
Date: Tue, 24 Jun 2025 06:43:35 +0200 [thread overview]
Message-ID: <63af6d5b-79d7-42a4-9d74-ed533c383a3d@linaro.org> (raw)
In-Reply-To: <ZYSr456CZ0p_X9wv@eldamar.lan>
On 21/12/23 22:19, Salvatore Bonaccorso wrote:
> Hi Philippe,
>
> On Wed, Nov 09, 2022 at 08:43:19AM +0100, Philippe Mathieu-Daudé wrote:
>> On 8/11/22 21:57, Stefan Hajnoczi wrote:
>>> I've dropped the SDHCI CVE fix due to the CI failure.
>>>
>>> The rest of the commits are still in the staging tree and I plan to
>>> include them in v7.2.0-rc0.
>>
>> Thank you Stefan, sorry for not catching that failure sooner.
>
> I was looking through some older CVE's for qemu which are tracked
> still unfixed in Debian and noticed CVE-2022-3872 . Do you happen to
> know if the fix for CVE-2022-3872, the dropped one above, was ever
> fixed in another way? Or did that felt trough the cracks?
Doh... You are right, this totally slipped off my radar :/
next prev parent reply other threads:[~2025-06-24 4:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-08 18:33 [PULL 0/3] Memory/SDHCI/ParallelFlash patches for v7.2.0-rc0 Philippe Mathieu-Daudé
2022-11-08 18:33 ` [PULL 1/3] memory: Fix wrong end address dump Philippe Mathieu-Daudé
2022-11-08 18:33 ` [PULL 2/3] hw/sd/sdhci: Do not set Buf Wr Ena before writing block (CVE-2022-3872) Philippe Mathieu-Daudé
2022-11-08 18:33 ` [PULL 3/3] Revert "hw/block/pflash_cfi: Error out if dev length isn't power of 2" Philippe Mathieu-Daudé
2022-11-08 20:49 ` [PULL 0/3] Memory/SDHCI/ParallelFlash patches for v7.2.0-rc0 Stefan Hajnoczi
2022-11-08 20:57 ` Stefan Hajnoczi
2022-11-09 7:43 ` Philippe Mathieu-Daudé
2023-12-21 21:19 ` Salvatore Bonaccorso
2025-06-24 4:43 ` Philippe Mathieu-Daudé [this message]
2025-07-01 15:48 ` T K Sourabh
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=63af6d5b-79d7-42a4-9d74-ed533c383a3d@linaro.org \
--to=philmd@linaro.org \
--cc=bin.meng@windriver.com \
--cc=carnil@debian.org \
--cc=david@redhat.com \
--cc=hreitz@redhat.com \
--cc=kwolf@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peterx@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=sourabhtk37@gmail.com \
--cc=stefanha@gmail.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;
as well as URLs for NNTP newsgroup(s).