public inbox for linux-arch@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-kernel@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	stable@vger.kernel.org,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Dan Williams <dan.j.williams@intel.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	linux-arch@vger.kernel.org, kernel-hardening@lists.openwall.com,
	Andy Lutomirski <luto@kernel.org>,
	alan@linux.intel.com, David Woodhouse <dwmw@amazon.co.uk>,
	Jack Wang <jinpu.wang@profitbricks.com>
Subject: [PATCH 4.4 178/193] x86/syscall: Sanitize syscall table de-references under speculation
Date: Fri, 23 Feb 2018 19:26:51 +0100	[thread overview]
Message-ID: <20180223170354.028619665@linuxfoundation.org> (raw)
In-Reply-To: <20180223170325.997716448@linuxfoundation.org>

4.4-stable review patch.  If anyone has any objections, please let me know.

------------------

From: Dan Williams <dan.j.williams@intel.com>

(cherry picked from commit 2fbd7af5af8665d18bcefae3e9700be07e22b681)

The syscall table base is a user controlled function pointer in kernel
space. Use array_index_nospec() to prevent any out of bounds speculation.

While retpoline prevents speculating into a userspace directed target it
does not stop the pointer de-reference, the concern is leaking memory
relative to the syscall table base, by observing instruction cache
behavior.

Reported-by: Linus Torvalds <torvalds@linux-foundation.org>
Signed-off-by: Dan Williams <dan.j.williams@intel.com>
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Cc: linux-arch@vger.kernel.org
Cc: kernel-hardening@lists.openwall.com
Cc: gregkh@linuxfoundation.org
Cc: Andy Lutomirski <luto@kernel.org>
Cc: alan@linux.intel.com
Link: https://lkml.kernel.org/r/151727417984.33451.1216731042505722161.stgit@dwillia2-desk3.amr.corp.intel.com
Signed-off-by: David Woodhouse <dwmw@amazon.co.uk>
[jwang: port to 4.4, no syscall_64]
Signed-off-by: Jack Wang <jinpu.wang@profitbricks.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
---
 arch/x86/entry/common.c |    2 ++
 1 file changed, 2 insertions(+)

--- a/arch/x86/entry/common.c
+++ b/arch/x86/entry/common.c
@@ -20,6 +20,7 @@
 #include <linux/export.h>
 #include <linux/context_tracking.h>
 #include <linux/user-return-notifier.h>
+#include <linux/nospec.h>
 #include <linux/uprobes.h>
 
 #include <asm/desc.h>
@@ -381,6 +382,7 @@ __always_inline void do_syscall_32_irqs_
 	}
 
 	if (likely(nr < IA32_NR_syscalls)) {
+		nr = array_index_nospec(nr, IA32_NR_syscalls);
 		/*
 		 * It's possible that a 32-bit syscall implementation
 		 * takes a 64-bit parameter but nonetheless assumes that

  parent reply	other threads:[~2018-02-23 18:26 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20180223170325.997716448@linuxfoundation.org>
2018-02-23 18:26 ` [PATCH 4.4 173/193] Documentation: Document array_index_nospec Greg Kroah-Hartman
2018-02-23 18:26   ` Greg Kroah-Hartman
2018-02-23 18:26 ` [PATCH 4.4 174/193] array_index_nospec: Sanitize speculative array de-references Greg Kroah-Hartman
2018-02-23 18:26   ` Greg Kroah-Hartman
2018-02-23 18:26 ` [PATCH 4.4 175/193] x86: Implement array_index_mask_nospec Greg Kroah-Hartman
2018-02-23 18:26   ` Greg Kroah-Hartman
2018-02-23 18:26 ` [PATCH 4.4 176/193] x86: Introduce barrier_nospec Greg Kroah-Hartman
2018-02-23 18:26   ` Greg Kroah-Hartman
2018-02-23 18:26 ` [PATCH 4.4 177/193] x86/get_user: Use pointer masking to limit speculation Greg Kroah-Hartman
2018-02-23 18:26   ` Greg Kroah-Hartman
2018-02-23 18:26 ` Greg Kroah-Hartman [this message]
2018-02-23 18:26   ` [PATCH 4.4 178/193] x86/syscall: Sanitize syscall table de-references under speculation Greg Kroah-Hartman
2018-03-06 14:21   ` Jiri Slaby
2018-03-06 14:21     ` Jiri Slaby
2018-03-06 16:02     ` Jiri Slaby
2018-03-06 16:02       ` Jiri Slaby
2018-03-06 16:11     ` Jinpu Wang
2018-03-06 16:11       ` Jinpu Wang
2018-03-07  7:53       ` [PATCH stable-4.4] x86/syscall: Sanitize syscall table de-references under speculation fix Jiri Slaby
2018-03-07  7:53         ` Jiri Slaby
2018-03-07  7:55         ` Jiri Slaby
2018-03-07  7:55           ` Jiri Slaby
2018-03-07  7:56           ` [PATCH v2 " Jiri Slaby
2018-03-07  7:56             ` Jiri Slaby
2018-03-07 15:06             ` Greg KH
2018-03-07 15:06               ` Greg KH
2018-02-23 18:26 ` [PATCH 4.4 179/193] vfs, fdtable: Prevent bounds-check bypass via speculative execution Greg Kroah-Hartman
2018-02-23 18:26   ` Greg Kroah-Hartman
2018-02-23 18:26 ` [PATCH 4.4 180/193] nl80211: Sanitize array index in parse_txq_params Greg Kroah-Hartman
2018-02-23 18:26   ` Greg Kroah-Hartman
2018-02-23 18:26 ` [PATCH 4.4 181/193] x86/spectre: Report get_user mitigation for spectre_v1 Greg Kroah-Hartman
2018-02-23 18:26   ` Greg Kroah-Hartman

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=20180223170354.028619665@linuxfoundation.org \
    --to=gregkh@linuxfoundation.org \
    --cc=alan@linux.intel.com \
    --cc=dan.j.williams@intel.com \
    --cc=dwmw@amazon.co.uk \
    --cc=jinpu.wang@profitbricks.com \
    --cc=kernel-hardening@lists.openwall.com \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.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