From: Thomas Huth <thuth@redhat.com>
To: "Philippe Mathieu-Daudé" <philmd@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
qemu-devel@nongnu.org
Cc: "Michael S. Tsirkin" <mst@redhat.com>,
mdroth@linux.vnet.ibm.com, qemu-stable@nongnu.org
Subject: Re: [PATCH] hw/core/loader: Fix possible crash in rom_copy()
Date: Thu, 26 Sep 2019 07:53:31 +0200 [thread overview]
Message-ID: <05bd2df7-afb7-039a-4d12-4cb41f0af211@redhat.com> (raw)
In-Reply-To: <ca146886-12e5-14c7-7b18-76494b1d7c8f@redhat.com>
On 25/09/2019 22.51, Philippe Mathieu-Daudé wrote:
> Hi Thomas,
>
> On 9/25/19 3:03 PM, Thomas Huth wrote:
>> Both, "rom->addr" and "addr" are derived from the binary image
>> that can be loaded with the "-kernel" paramer. The code in
>> rom_copy() then calculates:
>>
>> d = dest + (rom->addr - addr);
>>
>> and uses "d" as destination in a memcpy() some lines later. Now with
>> bad kernel images, it is possible that rom->addr is smaller than addr,
>> thus "rom->addr - addr" gets negative and the memcpy() then tries to
>> copy contents from the image to a bad memory location. In the best case,
>> this just crashes QEMU, in the worst case, this could maybe be used to
>> inject code from the kernel image into the QEMU binary, so we better fix
>> it with an additional sanity check here.
>>
>> Cc: qemu-stable@nongnu.org
>> Reported-by: Guangming Liu
>> Buglink: https://bugs.launchpad.net/qemu/+bug/1844635
>
> "This page does not exist, or you may not have permission to see it."
>
> This seems security related. Shouldn't we open a CVE for this?
> https://wiki.qemu.org/SecurityProcess#CVE_allocation
I wrote to the security team before writing the patch, so I assume a CVE
number is already on the way. I'll reply to this thread when it is
available.
Thomas
next prev parent reply other threads:[~2019-09-26 5:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-25 13:03 [PATCH] hw/core/loader: Fix possible crash in rom_copy() Thomas Huth
2019-09-25 13:22 ` Michael S. Tsirkin
2019-09-25 13:51 ` Paolo Bonzini
2019-09-25 20:51 ` Philippe Mathieu-Daudé
2019-09-26 5:53 ` Thomas Huth [this message]
2019-09-26 5:58 ` Thomas Huth
2019-09-26 6:11 ` Philippe Mathieu-Daudé
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=05bd2df7-afb7-039a-4d12-4cb41f0af211@redhat.com \
--to=thuth@redhat.com \
--cc=mdroth@linux.vnet.ibm.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=philmd@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).