From: Jon Maloy <jmaloy@redhat.com>
To: Thomas Huth <thuth@redhat.com>, qemu-devel@nongnu.org, f4bug@amsat.org
Cc: "Kevin Wolf" <kwolf@redhat.com>,
"Laurent Vivier" <lvivier@redhat.com>,
"Prasad J Pandit" <pjp@fedoraproject.org>,
qemu-block@nongnu.org, "Darren Kenny" <darren.kenny@oracle.com>,
"Alexander Bulekov" <alxndr@bu.edu>,
"Hanna Reitz" <hreitz@redhat.com>,
"Hervé Poussineau" <hpoussin@reactos.org>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"John Snow" <jsnow@redhat.com>
Subject: Re: [PATCH-for-6.2 0/2] hw/block/fdc: Fix CVE-2021-3507
Date: Thu, 10 Mar 2022 12:53:18 -0500 [thread overview]
Message-ID: <38386efc-1e83-63d4-703d-10c7650e7829@redhat.com> (raw)
In-Reply-To: <01a68a16-fa01-e7f3-4248-fdec6595cf74@redhat.com>
On 3/10/22 12:14, Thomas Huth wrote:
> On 06/02/2022 20.19, Jon Maloy wrote:
>> Trying again with correct email address.
>> ///jon
>>
>> On 2/6/22 14:15, Jon Maloy wrote:
>>>
>>>
>>> On 1/27/22 15:14, Jon Maloy wrote:
>>>>
>>>> On 11/18/21 06:57, Philippe Mathieu-Daudé wrote:
>>>>> Trivial fix for CVE-2021-3507.
>>>>>
>>>>> Philippe Mathieu-Daudé (2):
>>>>> hw/block/fdc: Prevent end-of-track overrun (CVE-2021-3507)
>>>>> tests/qtest/fdc-test: Add a regression test for CVE-2021-3507
>>>>>
>>>>> hw/block/fdc.c | 8 ++++++++
>>>>> tests/qtest/fdc-test.c | 20 ++++++++++++++++++++
>>>>> 2 files changed, 28 insertions(+)
>>>>>
>>>> Series
>>>> Acked-by: Jon Maloy <jmaloy@redhat.com>
>>>
>>> Philippe,
>>> I hear from other sources that you earlier have qualified this one
>>> as "incomplete".
>>> I am of course aware that this one, just like my own patch, is just
>>> a mitigation and not a complete correction of the erroneous
>>> calculation.
>>> Or did you have anything else in mind?
>
> Any news on this one? It would be nice to get the CVE fixed for 7.0 ?
>
> Thomas
>
The ball is currently with John Snow, as I understand it.
The concern is that this fix may not take the driver back to a
consistent state, so that we may have other problems later.
Maybe Philippe can chip in with a comment here?
///jon
next prev parent reply other threads:[~2022-03-10 17:55 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-18 11:57 [PATCH-for-6.2 0/2] hw/block/fdc: Fix CVE-2021-3507 Philippe Mathieu-Daudé
2021-11-18 11:57 ` [PATCH-for-6.2 1/2] hw/block/fdc: Prevent end-of-track overrun (CVE-2021-3507) Philippe Mathieu-Daudé
2021-11-23 15:56 ` Hanna Reitz
2021-11-18 11:57 ` [PATCH-for-6.2 2/2] tests/qtest/fdc-test: Add a regression test for CVE-2021-3507 Philippe Mathieu-Daudé
2021-11-23 16:04 ` Alexander Bulekov
2021-11-23 16:08 ` Hanna Reitz
2021-11-24 23:27 ` John Snow
2021-11-22 14:54 ` [PATCH-for-6.2 0/2] hw/block/fdc: Fix CVE-2021-3507 Philippe Mathieu-Daudé
2022-01-27 20:14 ` Jon Maloy
2022-02-04 21:39 ` John Snow
2022-02-06 19:15 ` Jon Maloy
2022-02-06 19:19 ` Jon Maloy
2022-03-10 17:14 ` Thomas Huth
2022-03-10 17:53 ` Jon Maloy [this message]
2022-03-18 18:50 ` Thomas Huth
2022-03-23 2:25 ` John Snow
2022-05-03 9:59 ` Kevin Wolf
2022-05-03 16:21 ` Jon Maloy
2022-05-12 11:06 ` Kevin Wolf
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=38386efc-1e83-63d4-703d-10c7650e7829@redhat.com \
--to=jmaloy@redhat.com \
--cc=alxndr@bu.edu \
--cc=darren.kenny@oracle.com \
--cc=f4bug@amsat.org \
--cc=hpoussin@reactos.org \
--cc=hreitz@redhat.com \
--cc=jsnow@redhat.com \
--cc=kwolf@redhat.com \
--cc=lvivier@redhat.com \
--cc=pbonzini@redhat.com \
--cc=pjp@fedoraproject.org \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.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).