From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: Li Qiang <liq3ea@gmail.com>,
keith.busch@intel.com, kwolf@redhat.com, mreitz@redhat.com
Cc: pbonzini@redhat.com, qemu-devel@nongnu.org,
qemu-block@nongnu.org, ppandit@redhat.com
Subject: Re: [Qemu-devel] [PATCH] nvme: fix oob access issue(CVE-2018-16847)
Date: Fri, 2 Nov 2018 08:51:56 +0100 [thread overview]
Message-ID: <db1c6887-8c1d-62e5-8363-2b775892ed6f@redhat.com> (raw)
In-Reply-To: <1541121763-3277-1-git-send-email-liq3ea@gmail.com>
On 2/11/18 2:22, Li Qiang wrote:
> Currently, the nvme_cmb_ops mr doesn't check the addr and size.
> This can lead an oob access issue. This is triggerable in the guest.
> Add check to avoid this issue.
>
> Fixes CVE-2018-16847.
>
> Reported-by: Li Qiang <liq3ea@gmail.com>
> Reviewed-by: Paolo Bonzini <pbonzini@redhat.com>
> Signed-off-by: Li Qiang <liq3ea@gmail.com>
> ---
> hw/block/nvme.c | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/hw/block/nvme.c b/hw/block/nvme.c
> index fc7dacb..d097add 100644
> --- a/hw/block/nvme.c
> +++ b/hw/block/nvme.c
> @@ -1175,6 +1175,10 @@ static void nvme_cmb_write(void *opaque, hwaddr addr, uint64_t data,
> unsigned size)
> {
> NvmeCtrl *n = (NvmeCtrl *)opaque;
> +
> + if (addr + size > NVME_CMBSZ_GETSIZE(n->bar.cmbsz)) {
Should this be reported via qemu_log_mask(LOG_GUEST_ERROR, ...)?
> + return;
> + }
> memcpy(&n->cmbuf[addr], &data, size);
> }
>
> @@ -1183,6 +1187,9 @@ static uint64_t nvme_cmb_read(void *opaque, hwaddr addr, unsigned size)
> uint64_t val;
> NvmeCtrl *n = (NvmeCtrl *)opaque;
>
> + if (addr + size > NVME_CMBSZ_GETSIZE(n->bar.cmbsz)) {
Ditto.
> + return 0;
> + }
> memcpy(&val, &n->cmbuf[addr], size);
> return val;
> }
>
next prev parent reply other threads:[~2018-11-02 7:52 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-02 1:22 [Qemu-devel] [PATCH] nvme: fix oob access issue(CVE-2018-16847) Li Qiang
2018-11-02 7:51 ` Philippe Mathieu-Daudé [this message]
2018-11-02 10:54 ` Kevin Wolf
2018-11-02 15:00 ` Keith Busch
2018-11-02 15:22 ` Li Qiang
2018-11-02 15:42 ` Kevin Wolf
2018-11-05 1:49 ` Li Qiang
2018-11-02 15:40 ` Keith Busch
2018-11-05 1:56 ` Li Qiang
2018-11-13 18:26 ` Paolo Bonzini
2018-11-13 1:45 ` Li Qiang
2018-11-13 10:17 ` Kevin Wolf
2018-11-13 10:24 ` Li Qiang
2018-11-13 18:27 ` Paolo Bonzini
2018-11-14 1:38 ` Li Qiang
2018-11-14 15:44 ` Paolo Bonzini
2018-11-15 3:14 ` Li Qiang
2018-11-15 18:10 ` Paolo Bonzini
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=db1c6887-8c1d-62e5-8363-2b775892ed6f@redhat.com \
--to=philmd@redhat.com \
--cc=keith.busch@intel.com \
--cc=kwolf@redhat.com \
--cc=liq3ea@gmail.com \
--cc=mreitz@redhat.com \
--cc=pbonzini@redhat.com \
--cc=ppandit@redhat.com \
--cc=qemu-block@nongnu.org \
--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).