All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] virtio-blk: refuse SG_IO requests with scsi=off
Date: Fri, 13 Jan 2012 10:54:57 -0600	[thread overview]
Message-ID: <4F1061E1.2050308@codemonkey.ws> (raw)
In-Reply-To: <1324651143-5247-1-git-send-email-pbonzini@redhat.com>

On 12/23/2011 08:39 AM, Paolo Bonzini wrote:
> QEMU does have a "scsi" option (to be used like -device
> virtio-blk-pci,drive=foo,scsi=off).  However, it only
> masks the feature bit, and does not reject the command
> if a malicious guest disregards the feature bits and
> issues a request.
>
> Without this patch, using scsi=off does not protect you
> from CVE-2011-4127.
>
> Signed-off-by: Paolo Bonzini<pbonzini@redhat.com>

Applied.  Thanks.

Regards,

Anthony Liguori

> ---
>   hw/virtio-blk.c |    6 ++++++
>   1 files changed, 6 insertions(+), 0 deletions(-)
>
> diff --git a/hw/virtio-blk.c b/hw/virtio-blk.c
> index b70d116..6cd3164 100644
> --- a/hw/virtio-blk.c
> +++ b/hw/virtio-blk.c
> @@ -153,6 +153,12 @@ static void virtio_blk_handle_scsi(VirtIOBlockReq *req)
>       int status;
>       int i;
>
> +    if ((req->dev->vdev.guest_features&  (1<<  VIRTIO_BLK_F_SCSI)) == 0) {
> +        virtio_blk_req_complete(req, VIRTIO_BLK_S_UNSUPP);
> +        g_free(req);
> +        return;
> +    }
> +
>       /*
>        * We require at least one output segment each for the virtio_blk_outhdr
>        * and the SCSI command block.

      parent reply	other threads:[~2012-01-13 16:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-23 14:39 [Qemu-devel] [PATCH] virtio-blk: refuse SG_IO requests with scsi=off Paolo Bonzini
2011-12-30 11:45 ` Stefan Hajnoczi
2012-01-05 10:05 ` Paolo Bonzini
2012-01-13 15:56   ` Paolo Bonzini
2012-01-13 16:54 ` Anthony Liguori [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=4F1061E1.2050308@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=pbonzini@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 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.