From: David Buchanan <d@vidbuchanan.co.uk>
To: Gerd Hoffmann <kraxel@redhat.com>, qemu-devel@nongnu.org
Cc: P J P <ppandit@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v2] vga: stop passing pointers to vga_draw_line* functions
Date: Mon, 9 Oct 2017 12:55:29 +0100 [thread overview]
Message-ID: <e64a628c-3377-f3f5-0646-079a2a175354@vidbuchanan.co.uk> (raw)
In-Reply-To: <20170828122906.18993-1-kraxel@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 393 bytes --]
I might be mistaken, but I don't think this patch actually fixes
CVE-2017-13672. I tested the latest git repo (last commit 530049bc1d)
against my initial reproducer, and QEMU still segfaults.
I think this is because the actual OOB read occurs inside pixman, which
of course is not affected by this patch. Perhaps bounds checks need to
be applied to the arguments passed into pixman?
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2017-10-09 11:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-28 12:29 [Qemu-devel] [PATCH v2] vga: stop passing pointers to vga_draw_line* functions Gerd Hoffmann
2017-10-09 11:55 ` David Buchanan [this message]
2017-10-09 12:56 ` Gerd Hoffmann
2017-10-09 13:09 ` David Buchanan
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=e64a628c-3377-f3f5-0646-079a2a175354@vidbuchanan.co.uk \
--to=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 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.