From: "Michael S. Tsirkin" <mst@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] late self-nomination
Date: Wed, 3 Aug 2016 01:44:38 +0300 [thread overview]
Message-ID: <20160803014330-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <758189906.13127402.1470164413674.JavaMail.zimbra@redhat.com>
On Tue, Aug 02, 2016 at 03:00:13PM -0400, Paolo Bonzini wrote:
> > > On x86 with VMX, the EPT page tables have separate R, W, and X bits.
> > > If a hypervisor were to limit the guest physical address space to the
> > > lower half (high bit always clear) and then alias all of it with the
> > > high guest physical address bit set and R clear, then the guest could
> > > use the high physical address bit as an effective R bit. That would
> > > allow PROT_WRITE, PROT_EXEC, and PROT_WRITE|PROT_EXEC mappings to work
> > > without granting read access.
> > >
> > > Doing this would provide some protection against attacks that use a
> > > wild read to scan for code or data structures at otherwise
> > > unpredictable addresses or to blindly search for ROP gadgets.
> >
> > Thanks - I expect we'll discuss this topic with other kvm folks quite a
> > bit on the kvm forum end of August, as well.
>
> I won't be able to attend kernel summit (I haven't nominated me for this
> reason) so I support Michael's presence!
>
> Paolo
I didn't realize. In that case I might be able to also give some
kind of summary from the kvm forum as well, if there's interest.
--
MST
prev parent reply other threads:[~2016-08-02 22:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-02 17:23 Michael S. Tsirkin
2016-08-02 17:28 ` Andy Lutomirski
2016-08-02 17:37 ` Michael S. Tsirkin
2016-08-02 19:00 ` Paolo Bonzini
2016-08-02 22:44 ` Michael S. Tsirkin [this message]
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=20160803014330-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=pbonzini@redhat.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