From: Fam Zheng <famz@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel@nongnu.org, qemu-stable@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] scsi: fix buffer overflow in scsi_req_parse_cdb (CVE-2015-5158)
Date: Thu, 23 Jul 2015 09:35:33 +0800 [thread overview]
Message-ID: <20150723013533.GA7334@ad.nay.redhat.com> (raw)
In-Reply-To: <1437574681-18362-1-git-send-email-pbonzini@redhat.com>
On Wed, 07/22 16:18, Paolo Bonzini wrote:
> This is a guest-triggerable buffer overflow present in QEMU 2.2.0
> and newer. scsi_cdb_length returns -1 as an error value, but the
> caller does not check it.
>
> Luckily, the massive overflow means that QEMU will just SIGSEGV,
> making the impact much smaller.
>
> Reported-by: Zhu Donghai (朱东海) <donghai.zdh@alibaba-inc.com>
> Fixes: 1894df02811f6b79ea3ffbf1084599d96f316173
> Cc: qemu-stable@nongnu.org
> ---
> hw/scsi/scsi-bus.c | 7 ++++++-
> 1 file changed, 6 insertions(+), 1 deletion(-)
>
> diff --git a/hw/scsi/scsi-bus.c b/hw/scsi/scsi-bus.c
> index f50b2f0..f0ae462 100644
> --- a/hw/scsi/scsi-bus.c
> +++ b/hw/scsi/scsi-bus.c
> @@ -1239,10 +1239,15 @@ int scsi_cdb_length(uint8_t *buf) {
> int scsi_req_parse_cdb(SCSIDevice *dev, SCSICommand *cmd, uint8_t *buf)
> {
> int rc;
> + int len;
>
> cmd->lba = -1;
> - cmd->len = scsi_cdb_length(buf);
> + len = scsi_cdb_length(buf);
> + if (len < 0) {
> + return -1;
> + }
>
> + cmd->len = len;
> switch (dev->type) {
> case TYPE_TAPE:
> rc = scsi_req_stream_xfer(cmd, dev, buf);
> --
> 2.4.3
>
>
Reviewed-by: Fam Zheng <famz@redhat.com>
prev parent reply other threads:[~2015-07-23 1:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-22 14:18 [Qemu-devel] [PATCH] scsi: fix buffer overflow in scsi_req_parse_cdb (CVE-2015-5158) Paolo Bonzini
2015-07-22 14:27 ` Daniel P. Berrange
2015-07-22 16:22 ` Paolo Bonzini
2015-07-23 1:35 ` Fam Zheng [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=20150723013533.GA7334@ad.nay.redhat.com \
--to=famz@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@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).