From: Peter Maydell <peter.maydell@linaro.org>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: Petr Matousek <pmatouse@redhat.com>,
QEMU Developers <qemu-devel@nongnu.org>,
"Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [Qemu-devel] [PATCH][XSA-126] xen: limit guest control of PCI command register
Date: Fri, 10 Apr 2015 12:45:23 +0100 [thread overview]
Message-ID: <CAFEAcA_zwz6mbRKvE9aFgrP0bttZy1-Ce4jTLNBLuScZRw4Byg@mail.gmail.com> (raw)
In-Reply-To: <CAFEAcA-Om3M=qF8Dso92nEhZebdm8n1h8o3Kw8NxZXVChQr6BA@mail.gmail.com>
On 9 April 2015 at 19:10, Peter Maydell <peter.maydell@linaro.org> wrote:
> On 31 March 2015 at 15:18, Stefano Stabellini
> <stefano.stabellini@eu.citrix.com> wrote:
>> From: Jan Beulich <jbeulich@suse.com>
>>
>> Otherwise the guest can abuse that control to cause e.g. PCIe
>> Unsupported Request responses (by disabling memory and/or I/O decoding
>> and subsequently causing [CPU side] accesses to the respective address
>> ranges), which (depending on system configuration) may be fatal to the
>> host.
>>
>> This is CVE-2015-2756 / XSA-126.
>>
>> Signed-off-by: Jan Beulich <jbeulich@suse.com>
>> Reviewed-by: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
>> Acked-by: Ian Campbell <ian.campbell@citrix.com>
>
> Oops, this one got lost. I'm going to commit it to qemu master tomorrow
> (so it will go in -rc3), unless there are objections (I can't
> really tell from the thread what the conclusion of the discussion
> was).
Committed.
-- PMM
next prev parent reply other threads:[~2015-04-10 12:16 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-31 14:18 [Qemu-devel] [PATCH][XSA-126] xen: limit guest control of PCI command register Stefano Stabellini
2015-04-01 9:01 ` Michael S. Tsirkin
2015-04-01 9:20 ` Stefano Stabellini
2015-04-01 9:32 ` Michael S. Tsirkin
2015-04-01 9:41 ` [Qemu-devel] [Xen-devel] " Andrew Cooper
2015-04-01 9:59 ` Michael S. Tsirkin
2015-04-13 8:17 ` Jan Beulich
2015-04-13 11:19 ` Michael S. Tsirkin
2015-04-13 11:34 ` Jan Beulich
2015-04-13 11:47 ` Michael S. Tsirkin
2015-04-13 12:40 ` Jan Beulich
2015-04-13 12:47 ` Michael S. Tsirkin
2015-04-13 12:51 ` Jan Beulich
2015-04-20 13:43 ` Michael S. Tsirkin
2015-04-20 14:08 ` Jan Beulich
2015-04-20 14:32 ` Michael S. Tsirkin
2015-04-20 14:57 ` Jan Beulich
2015-06-07 6:23 ` Michael S. Tsirkin
2015-06-08 7:42 ` Jan Beulich
2015-06-08 8:09 ` Malcolm Crossley
2015-06-08 8:59 ` Michael S. Tsirkin
2015-06-08 9:03 ` Jan Beulich
2015-06-08 9:36 ` Michael S. Tsirkin
2015-06-08 10:55 ` Jan Beulich
2015-06-08 11:28 ` Michael S. Tsirkin
2015-06-08 11:44 ` Jan Beulich
2015-06-10 7:00 ` Jan Beulich
2015-06-10 11:43 ` Michael S. Tsirkin
2015-06-10 12:06 ` Jan Beulich
2015-06-10 13:35 ` Michael S. Tsirkin
2015-06-08 9:30 ` Michael S. Tsirkin
2015-06-08 10:38 ` Jan Beulich
2015-06-10 7:08 ` Jan Beulich
2015-06-10 11:46 ` Michael S. Tsirkin
2015-06-10 12:10 ` Jan Beulich
2015-04-01 9:50 ` Ian Campbell
2015-04-01 10:12 ` Michael S. Tsirkin
2015-04-09 18:10 ` [Qemu-devel] " Peter Maydell
2015-04-10 11:45 ` Peter Maydell [this message]
2015-04-10 11:49 ` Peter Maydell
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=CAFEAcA_zwz6mbRKvE9aFgrP0bttZy1-Ce4jTLNBLuScZRw4Byg@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=mst@redhat.com \
--cc=pmatouse@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefano.stabellini@eu.citrix.com \
/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).