xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Norbert Manthey <nmanthey@amazon.de>
To: xen-devel@lists.xenproject.org
Cc: Juergen Gross <jgross@suse.com>, Tim Deegan <tim@xen.org>,
	Stefano Stabellini <sstabellini@kernel.org>,
	Wei Liu <wei.liu2@citrix.com>,
	Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
	George Dunlap <George.Dunlap@eu.citrix.com>,
	Andrew Cooper <andrew.cooper3@citrix.com>,
	Ian Jackson <ian.jackson@eu.citrix.com>,
	Dario Faggioli <dfaggioli@suse.com>,
	Martin Pohlack <mpohlack@amazon.de>,
	Pawel Wieczorkiewicz <wipawel@amazon.de>,
	Julien Grall <julien.grall@arm.com>,
	David Woodhouse <dwmw@amazon.co.uk>,
	Jan Beulich <jbeulich@suse.com>,
	Martin Mazein <amazein@amazon.de>,
	Bjoern Doebel <doebel@amazon.de>,
	Norbert Manthey <nmanthey@amazon.de>
Subject: [PATCH L1TF v10 5/8] common/memory: block speculative out-of-bound accesses
Date: Thu, 14 Mar 2019 13:50:08 +0100	[thread overview]
Message-ID: <1552567811-5301-6-git-send-email-nmanthey@amazon.de> (raw)
In-Reply-To: <1552567811-5301-1-git-send-email-nmanthey@amazon.de>

The get_page_from_gfn method returns a pointer to a page that belongs
to a gfn. Before returning the pointer, the gfn is checked for being
valid. Under speculation, these checks can be bypassed, so that
the function get_page is still executed partially. Consequently, the
function page_get_owner_and_reference might be executed partially as
well. In this function, the computed pointer is accessed, resulting in
a speculative out-of-bound address load. As the gfn can be controlled by
a guest, this access is problematic.

To mitigate the root cause, an lfence instruction is added via the
evaluate_nospec macro. To make the protection generic, we do not
introduce the lfence instruction for this single check, but add it to
the mfn_valid function. This way, other potentially problematic accesses
are protected as well.

This is part of the speculative hardening effort.

Signed-off-by: Norbert Manthey <nmanthey@amazon.de>
Acked-by: Jan Beulich <jbeulich@suse.com>

---
 xen/common/pdx.c | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/xen/common/pdx.c b/xen/common/pdx.c
--- a/xen/common/pdx.c
+++ b/xen/common/pdx.c
@@ -18,6 +18,7 @@
 #include <xen/init.h>
 #include <xen/mm.h>
 #include <xen/bitops.h>
+#include <xen/nospec.h>
 
 /* Parameters for PFN/MADDR compression. */
 unsigned long __read_mostly max_pdx;
@@ -33,8 +34,9 @@ unsigned long __read_mostly pdx_group_valid[BITS_TO_LONGS(
 
 bool __mfn_valid(unsigned long mfn)
 {
-    return likely(mfn < max_page) &&
-           likely(!(mfn & pfn_hole_mask)) &&
+    if ( unlikely(evaluate_nospec(mfn >= max_page)) )
+        return false;
+    return likely(!(mfn & pfn_hole_mask)) &&
            likely(test_bit(pfn_to_pdx(mfn) / PDX_GROUP_COUNT,
                            pdx_group_valid));
 }
-- 
2.7.4




Amazon Development Center Germany GmbH
Krausenstr. 38
10117 Berlin
Geschaeftsfuehrer: Christian Schlaeger, Ralf Herbrich
Ust-ID: DE 289 237 879
Eingetragen am Amtsgericht Charlottenburg HRB 149173 B



_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

  parent reply	other threads:[~2019-03-14 12:53 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-14 12:50 L1TF Patch Series v10 Norbert Manthey
2019-03-14 12:50 ` [PATCH L1TF v10 1/8] spec: add l1tf-barrier Norbert Manthey
2019-03-14 12:50 ` [PATCH L1TF v10 2/8] nospec: introduce evaluate_nospec Norbert Manthey
2019-03-14 13:19   ` Jan Beulich
2019-03-14 13:21     ` Norbert Manthey
2019-03-14 12:50 ` [PATCH L1TF v10 3/8] is_control_domain: block speculation Norbert Manthey
2019-03-14 12:50 ` [PATCH L1TF v10 4/8] is_hvm/pv_domain: " Norbert Manthey
2019-04-05 15:34   ` Andrew Cooper
2019-04-05 15:34     ` [Xen-devel] " Andrew Cooper
2019-04-05 18:29     ` Norbert Manthey
2019-04-05 18:29       ` [Xen-devel] " Norbert Manthey
2019-04-05 18:38       ` Andrew Cooper
2019-04-05 18:38         ` [Xen-devel] " Andrew Cooper
2019-04-08  9:19       ` Jan Beulich
2019-04-08  9:19         ` [Xen-devel] " Jan Beulich
2019-03-14 12:50 ` Norbert Manthey [this message]
2019-03-14 12:50 ` [PATCH L1TF v10 6/8] x86/hvm: add nospec to hvmop param Norbert Manthey
2019-03-14 12:50 ` [PATCH L1TF v10 7/8] common/grant_table: block speculative out-of-bound accesses Norbert Manthey
2019-03-29 17:11   ` Jan Beulich
2019-05-20 14:27     ` Norbert Manthey
2019-05-20 14:27       ` [Xen-devel] " Norbert Manthey
2019-05-21  9:41       ` Jan Beulich
2019-05-21  9:41         ` [Xen-devel] " Jan Beulich
2019-03-14 12:50 ` [PATCH L1TF v10 8/8] common/domain: " Norbert Manthey
2019-03-14 13:20   ` 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=1552567811-5301-6-git-send-email-nmanthey@amazon.de \
    --to=nmanthey@amazon.de \
    --cc=George.Dunlap@eu.citrix.com \
    --cc=amazein@amazon.de \
    --cc=andrew.cooper3@citrix.com \
    --cc=dfaggioli@suse.com \
    --cc=doebel@amazon.de \
    --cc=dwmw@amazon.co.uk \
    --cc=ian.jackson@eu.citrix.com \
    --cc=jbeulich@suse.com \
    --cc=jgross@suse.com \
    --cc=julien.grall@arm.com \
    --cc=konrad.wilk@oracle.com \
    --cc=mpohlack@amazon.de \
    --cc=sstabellini@kernel.org \
    --cc=tim@xen.org \
    --cc=wei.liu2@citrix.com \
    --cc=wipawel@amazon.de \
    --cc=xen-devel@lists.xenproject.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).