From: Juan Quintela <quintela@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: qemu-devel@nongnu.org, Anthony Liguori <aliguori@amazon.com>
Subject: Re: [Qemu-devel] [PATCH v6 4/5] virtio: validate config_len on load
Date: Mon, 05 May 2014 16:22:53 +0200 [thread overview]
Message-ID: <87tx94nw3m.fsf@elfo.mitica> (raw)
In-Reply-To: <87y4ygnwoe.fsf@elfo.mitica> (Juan Quintela's message of "Mon, 05 May 2014 16:10:25 +0200")
Juan Quintela <quintela@redhat.com> wrote:
> "Michael S. Tsirkin" <mst@redhat.com> wrote:
>> Malformed input can have config_len in migration stream
>> exceed the array size allocated on destination, the
>> result will be heap overflow.
>>
>> To fix, that config_len matches on both sides.
>>
>> CVE-2014-0182
>>
>> Reported-by: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
>> Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
>> ---
>> hw/virtio/virtio.c | 8 +++++++-
>> 1 file changed, 7 insertions(+), 1 deletion(-)
>>
>> diff --git a/hw/virtio/virtio.c b/hw/virtio/virtio.c
>> index 3bad71e..0d5d368 100644
>> --- a/hw/virtio/virtio.c
>> +++ b/hw/virtio/virtio.c
>> @@ -898,6 +898,7 @@ int virtio_set_features(VirtIODevice *vdev, uint32_t val)
>> int virtio_load(VirtIODevice *vdev, QEMUFile *f)
>> {
>> int i, ret;
>> + int32_t config_len;
>
> Has a warning.
>
> /mnt/kvm/qemu/next/hw/virtio/virtio.c: In function ‘virtio_load’:
> /mnt/kvm/qemu/next/hw/virtio/virtio.c:931:22: error: format ‘%i’
> expects argument of type ‘int’, but argument 2 has type ‘size_t’
> [-Werror=format=]
> config_len, vdev->config_len);
> ^
>
> changing config_len to size_t.
After discussing with michael, left it as int32_t
>
>> uint32_t num;
>> uint32_t features;
>> uint32_t supported_features;
>> @@ -924,7 +925,12 @@ int virtio_load(VirtIODevice *vdev, QEMUFile *f)
>> features, supported_features);
>> return -1;
>> }
>> - vdev->config_len = qemu_get_be32(f);
>> + config_len = qemu_get_be32(f);
>> + if (config_len != vdev->config_len) {
>> + error_report("Unexpected config length 0x%x. Expected 0x%x",
>
> and this to:
>
> s/%x/%zx/
and use here "%ix .... %zx"
Later, Juan.
> Later, Juan.
>
>
>> + config_len, vdev->config_len);
>> + return -1;
>> + }
>> qemu_get_buffer(f, vdev->config, vdev->config_len);
>>
>> num = qemu_get_be32(f);
prev parent reply other threads:[~2014-05-05 14:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1398690327-7838-1-git-send-email-mst@redhat.com>
[not found] ` <1398690327-7838-5-git-send-email-mst@redhat.com>
2014-05-05 14:10 ` [Qemu-devel] [PATCH v6 4/5] virtio: validate config_len on load Juan Quintela
2014-05-05 14:22 ` Juan Quintela [this message]
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=87tx94nw3m.fsf@elfo.mitica \
--to=quintela@redhat.com \
--cc=aliguori@amazon.com \
--cc=mst@redhat.com \
--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).