From: Eric Blake <eblake@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>, qemu-devel@nongnu.org
Cc: d@vidbuchanan.co.uk, P J P <ppandit@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] vga: stop passing pointers to vga_draw_line* functions
Date: Thu, 24 Aug 2017 11:30:18 -0500 [thread overview]
Message-ID: <cd7ebf5c-6d81-6cdf-f6b2-87af4cb00f85@redhat.com> (raw)
In-Reply-To: <20170824091907.17676-1-kraxel@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1216 bytes --]
On 08/24/2017 04:19 AM, Gerd Hoffmann wrote:
> Instead pass around the address (aka offset into vga memory).
> Add vga_read_* helper functions which apply vbe_size_mask to
> the address, to make sure the address stays within the valid
> range, simliar to the cirrus blitter fixes (commits ffaf857778
s/simliar/similar/
> and 026aeffcb4).
>
> Impact: DoS for priviledged guest users. qemu crashes with
s/priviledged/privileged/
> a segfault, when hitting the guard page after vga memory
> allocation, while reading vga memory for display updates.
>
> Fixes: CVE-2017-xxxx
Do we have the actual number? Are we trying to get this in 2.10-rc4, or
is it merely 2.11 + qemu-stable (2.10.1) material?
> Cc: P J P <ppandit@redhat.com>
> Reported-by: David Buchanan <d@vidbuchanan.co.uk>
> Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
> ---
> hw/display/vga-helpers.h | 202 ++++++++++++++++++++++++++---------------------
> hw/display/vga_int.h | 1 +
> hw/display/vga.c | 5 +-
> 3 files changed, 114 insertions(+), 94 deletions(-)
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 619 bytes --]
next prev parent reply other threads:[~2017-08-24 16:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-24 9:19 [Qemu-devel] [PATCH] vga: stop passing pointers to vga_draw_line* functions Gerd Hoffmann
2017-08-24 16:30 ` Eric Blake [this message]
2017-08-25 11:22 ` Gerd Hoffmann
2017-08-28 10:29 ` P J P
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=cd7ebf5c-6d81-6cdf-f6b2-87af4cb00f85@redhat.com \
--to=eblake@redhat.com \
--cc=d@vidbuchanan.co.uk \
--cc=kraxel@redhat.com \
--cc=ppandit@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).