From: Cornelia Huck <cohuck@redhat.com>
To: Dima Stepanov <dimastep@yandex-team.ru>
Cc: mst@redhat.com, qemu-devel@nongnu.org, wrfsh@yandex-team.ru
Subject: Re: [Qemu-devel] [PATCH v1] virtio: add checks for the size of the indirect table
Date: Tue, 15 Jan 2019 11:40:09 +0100 [thread overview]
Message-ID: <20190115114009.0a09eac1.cohuck@redhat.com> (raw)
In-Reply-To: <1547546927-18006-1-git-send-email-dimastep@yandex-team.ru>
On Tue, 15 Jan 2019 13:08:47 +0300
Dima Stepanov <dimastep@yandex-team.ru> wrote:
> The virtqueue_pop() and virtqueue_get_avail_bytes() routines can use the
> INDIRECT table to get the data. It is possible to create a packet which
> will lead to the assert message like:
> include/exec/memory.h:1995: void
> address_space_read_cached(MemoryRegionCache *, hwaddr, void *, int):
> Assertion `addr < cache->len && len <= cache->len - addr' failed.
> Aborted
> To do it the first descriptor should have a link to the INDIRECT table
> and set the size of it to 0. It doesn't look good that the guest should
> be able to trigger the assert in qemu. Add additional check for the size
> of the INDIRECT table, which should not be 0.
Ouch, being able to crash QEMU by a specially crafted descriptor is bad.
Looking at the virtio spec, we don't seem to explicitly disallow
indirect descriptors with a zero-length table. So, as an alternative to
marking the device broken, we could also skip over such a descriptor.
Not sure whether that makes sense, though.
>
> Signed-off-by: Dima Stepanov <dimastep@yandex-team.ru>
> ---
> hw/virtio/virtio.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/hw/virtio/virtio.c b/hw/virtio/virtio.c
> index 22bd1ac..a1ff647 100644
> --- a/hw/virtio/virtio.c
> +++ b/hw/virtio/virtio.c
> @@ -646,7 +646,7 @@ void virtqueue_get_avail_bytes(VirtQueue *vq, unsigned int *in_bytes,
> vring_desc_read(vdev, &desc, desc_cache, i);
>
> if (desc.flags & VRING_DESC_F_INDIRECT) {
> - if (desc.len % sizeof(VRingDesc)) {
> + if (!desc.len || (desc.len % sizeof(VRingDesc))) {
> virtio_error(vdev, "Invalid size for indirect buffer table");
> goto err;
> }
> @@ -902,7 +902,7 @@ void *virtqueue_pop(VirtQueue *vq, size_t sz)
> desc_cache = &caches->desc;
> vring_desc_read(vdev, &desc, desc_cache, i);
> if (desc.flags & VRING_DESC_F_INDIRECT) {
> - if (desc.len % sizeof(VRingDesc)) {
> + if (!desc.len || (desc.len % sizeof(VRingDesc))) {
> virtio_error(vdev, "Invalid size for indirect buffer table");
> goto done;
> }
next prev parent reply other threads:[~2019-01-15 10:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-15 10:08 [Qemu-devel] [PATCH v1] virtio: add checks for the size of the indirect table Dima Stepanov
2019-01-15 10:36 ` Philippe Mathieu-Daudé
2019-01-15 10:40 ` Cornelia Huck [this message]
2019-01-15 13:11 ` Dima Stepanov
2019-01-15 13:38 ` Cornelia Huck
2019-01-15 19:05 ` Michael S. Tsirkin
2019-01-15 14:27 ` Stefan Hajnoczi
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=20190115114009.0a09eac1.cohuck@redhat.com \
--to=cohuck@redhat.com \
--cc=dimastep@yandex-team.ru \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=wrfsh@yandex-team.ru \
/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.