From: "Jan Beulich" <JBeulich@novell.com>
To: Tim Deegan <Tim.Deegan@citrix.com>
Cc: xen-devel@lists.xensource.com,
"Xen.org security team" <security@xen.org>
Subject: Re: Xen Advisory 5 (CVE-2011-3131) IOMMU fault livelock
Date: Fri, 12 Aug 2011 14:53:44 +0100 [thread overview]
Message-ID: <4E454C880200007800051000@nat28.tlf.novell.com> (raw)
In-Reply-To: <20037.10841.995717.397090@mariner.uk.xensource.com>
>>> On 12.08.11 at 15:27, Xen.org security team <security@xen.org> wrote:
> IMPACT
> ======
>
> A malicious guest administrator of a VM that has direct control of a
> PCI[E] device can cause a performance degradation, and possibly hang the
> host.
>
> RESOLUTION
> ==========
>
> This issue is resolved in changeset 23762:537ed3b74b3f of
> xen-unstable.hg, and 23112:84e3706df07a of xen-4.1-testing.hg.
Do you really think this helps much? Direct control of the device means
it could also (perhaps on a second vCPU) constantly re-enable the bus
mastering bit. Preventing that would need cooperation with pciback or
filtering of subsequent config space writes directly in the hypervisor
(the latter could become difficult when mmcfg is being used by Dom0
even for base accesses).
Jan
next prev parent reply other threads:[~2011-08-12 13:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-12 13:27 Xen Advisory 5 (CVE-2011-3131) IOMMU fault livelock Xen.org security team
2011-08-12 13:53 ` Jan Beulich [this message]
2011-08-12 14:09 ` Tim Deegan
2011-08-12 14:48 ` Jan Beulich
2011-08-15 9:26 ` Tim Deegan
2011-08-15 10:02 ` Jan Beulich
2011-08-16 7:03 ` Jan Beulich
2011-08-16 15:06 ` Tim Deegan
2011-08-16 15:59 ` Jan Beulich
2011-09-21 0:07 ` Kay, Allen M
2011-09-21 6:47 ` Jan Beulich
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=4E454C880200007800051000@nat28.tlf.novell.com \
--to=jbeulich@novell.com \
--cc=Tim.Deegan@citrix.com \
--cc=security@xen.org \
--cc=xen-devel@lists.xensource.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 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.