From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>, qemu-devel@nongnu.org
Cc: sstabellini@kernel.org, pmatouse@redhat.com,
"Michael S. Tsirkin" <mst@redhat.com>,
mdroth@linux.vnet.ibm.com, ppandit@redhat.com,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [PATCH 1/2] qxl: map rom r/o
Date: Tue, 25 Feb 2020 10:07:04 +0100 [thread overview]
Message-ID: <2bdcbe5f-1fa0-386d-a9c4-f0d7c2bebca1@redhat.com> (raw)
In-Reply-To: <20200225055920.17261-2-kraxel@redhat.com>
On 2/25/20 6:59 AM, Gerd Hoffmann wrote:
> Map qxl rom read-only into the guest, so the guest can't tamper with the
> content. qxl has a shadow copy of the rom to deal with that, but the
> shadow doesn't cover the mode list. A privilidged user in the guest can
> manipulate the mode list and that to trick qemu into oob reads, leading
> to a DoS via segfault if that read access happens to hit unmapped memory.
>
> Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
> ---
> hw/display/qxl.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/hw/display/qxl.c b/hw/display/qxl.c
> index 21a43a1d5ec2..227da69a50d9 100644
> --- a/hw/display/qxl.c
> +++ b/hw/display/qxl.c
> @@ -2136,7 +2136,7 @@ static void qxl_realize_common(PCIQXLDevice *qxl, Error **errp)
> pci_set_byte(&config[PCI_INTERRUPT_PIN], 1);
>
> qxl->rom_size = qxl_rom_size();
> - memory_region_init_ram(&qxl->rom_bar, OBJECT(qxl), "qxl.vrom",
> + memory_region_init_rom(&qxl->rom_bar, OBJECT(qxl), "qxl.vrom",
> qxl->rom_size, &error_fatal);
> init_qxl_rom(qxl);
> init_qxl_ram(qxl);
>
Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>
next prev parent reply other threads:[~2020-02-25 9:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-25 5:59 [PATCH 0/2] qxl: map rom r/o, remove shadow Gerd Hoffmann
2020-02-25 5:59 ` [PATCH 1/2] qxl: map rom r/o Gerd Hoffmann
2020-02-25 9:07 ` Philippe Mathieu-Daudé [this message]
2020-02-25 5:59 ` [PATCH 2/2] qxl: drop shadow_rom Gerd Hoffmann
2020-02-25 7:39 ` Paolo Bonzini
2020-02-25 8:23 ` Gerd Hoffmann
2020-02-25 8:29 ` 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=2bdcbe5f-1fa0-386d-a9c4-f0d7c2bebca1@redhat.com \
--to=philmd@redhat.com \
--cc=kraxel@redhat.com \
--cc=mdroth@linux.vnet.ibm.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=pmatouse@redhat.com \
--cc=ppandit@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=sstabellini@kernel.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).