From: Peter Lieven <pl@kamp.de>
To: Markus Armbruster <armbru@redhat.com>
Cc: peter.maydell@linaro.org, Petr Matousek <pmatouse@redhat.com>,
Stefan Weil <sw@weilnetz.de>,
qemu-devel@nongnu.org, qemu-stable@nongnu.org,
John Snow <jsnow@redhat.com>
Subject: Re: [Qemu-devel] [Qemu-stable] [PATCH] fdc: force the fifo access to be in bounds of the allocated buffer
Date: Wed, 13 May 2015 22:02:07 +0200 [thread overview]
Message-ID: <5553ADBF.6060005@kamp.de> (raw)
In-Reply-To: <877fsccl19.fsf@blackfin.pond.sub.org>
Am 13.05.2015 um 21:52 schrieb Markus Armbruster:
> Peter Lieven <pl@kamp.de> writes:
>
>> Am 13.05.2015 um 21:09 schrieb Stefan Priebe:
>>> Am 13.05.2015 um 21:05 schrieb Stefan Weil:
>>>> Am 13.05.2015 um 20:59 schrieb Stefan Priebe:
>>>>> Am 13.05.2015 um 20:51 schrieb Stefan Weil:
>>>>>> Hi,
>>>>>>
>>>>>> I just noticed this patch because my provider told me that my KVM based
>>>>>> server
>>>>>> needs a reboot because of a CVE (see this German news:
>>>>>> http://www.heise.de/newsticker/meldung/Venom-Schwachstelle-Aus-Hypervisor-ausbrechen-und-VMs-ausspionieren-2649614.html)
>>>>>>
>>>>> Isn't a live migration to a fixed version enough instead of a reboot?
>>>>>
>>>>> Stefan
>>>> Good point. A live migration would be sufficient - if there are no bugs
>>>> in QEMU's live migration.
>>> just migrating all our customer machines and wanted to be sure that
>>> live migration is enough.
>> Just to confirm: If Qemu is started with -nodefaults and there is no
>> fdc configuration the system is not affected by this CVE?
> Not true. The FD controller is still there. It has no drives attached
> then, but is vulnerable all the same.
Are you sure? With -nodefaults the hmp command 'info block' returns nothing and
the guest sees no floppy drive.
Without -nodefaults I indeed see floppy0 and I have /dev/fd0 in the guest respectively.
Peter
next prev parent reply other threads:[~2015-05-13 20:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-13 14:33 [Qemu-devel] [PATCH] fdc: force the fifo access to be in bounds of the allocated buffer John Snow
2015-05-13 14:33 ` John Snow
2015-05-13 14:35 ` John Snow
2015-05-13 18:51 ` Stefan Weil
2015-05-13 18:59 ` [Qemu-devel] [Qemu-stable] " Stefan Priebe
2015-05-13 19:04 ` John Snow
2015-05-13 19:06 ` Stefan Priebe
2015-05-13 19:05 ` Stefan Weil
2015-05-13 19:09 ` Stefan Priebe
2015-05-13 19:30 ` Peter Lieven
2015-05-13 19:52 ` Markus Armbruster
2015-05-13 20:02 ` Peter Lieven [this message]
2015-05-13 20:03 ` John Snow
2015-05-13 20:04 ` Peter Lieven
2015-05-13 20:54 ` [Qemu-devel] " John Snow
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=5553ADBF.6060005@kamp.de \
--to=pl@kamp.de \
--cc=armbru@redhat.com \
--cc=jsnow@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=pmatouse@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@nongnu.org \
--cc=sw@weilnetz.de \
/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).