From: Dan Williams <dan.j.williams@intel.com> To: linux-kernel@vger.kernel.org Cc: linux-arch@vger.kernel.org, kernel-hardening@lists.openwall.com, gregkh@linuxfoundation.org, x86@kernel.org, Ingo Molnar <mingo@redhat.com>, Andy Lutomirski <luto@kernel.org>, "H. Peter Anvin" <hpa@zytor.com>, tglx@linutronix.de, torvalds@linux-foundation.org, akpm@linux-foundation.org, alan@linux.intel.com Subject: [PATCH v4 07/10] x86: narrow out of bounds syscalls to sys_read under speculation Date: Thu, 18 Jan 2018 16:02:21 -0800 [thread overview] Message-ID: <151632014097.21271.16980532033566583357.stgit@dwillia2-desk3.amr.corp.intel.com> (raw) In-Reply-To: <151632009605.21271.11304291057104672116.stgit@dwillia2-desk3.amr.corp.intel.com> The syscall table base is a user controlled function pointer in kernel space. Like, 'get_user, use 'MASK_NOSPEC' to prevent any out of bounds speculation. While retpoline prevents speculating into the user controlled target it does not stop the pointer de-reference, the concern is leaking memory relative to the syscall table base. Reported-by: Linus Torvalds <torvalds@linux-foundation.org> Cc: Thomas Gleixner <tglx@linutronix.de> Cc: Ingo Molnar <mingo@redhat.com> Cc: "H. Peter Anvin" <hpa@zytor.com> Cc: x86@kernel.org Cc: Andy Lutomirski <luto@kernel.org> Signed-off-by: Dan Williams <dan.j.williams@intel.com> --- arch/x86/entry/entry_64.S | 2 ++ arch/x86/include/asm/smap.h | 9 ++++++++- 2 files changed, 10 insertions(+), 1 deletion(-) diff --git a/arch/x86/entry/entry_64.S b/arch/x86/entry/entry_64.S index 4f8e1d35a97c..2320017077d4 100644 --- a/arch/x86/entry/entry_64.S +++ b/arch/x86/entry/entry_64.S @@ -35,6 +35,7 @@ #include <asm/asm.h> #include <asm/smap.h> #include <asm/pgtable_types.h> +#include <asm/smap.h> #include <asm/export.h> #include <asm/frame.h> #include <asm/nospec-branch.h> @@ -264,6 +265,7 @@ entry_SYSCALL_64_fastpath: cmpl $__NR_syscall_max, %eax #endif ja 1f /* return -ENOSYS (already in pt_regs->ax) */ + MASK_NOSPEC %r11 %rax /* sanitize syscall_nr wrt speculation */ movq %r10, %rcx /* diff --git a/arch/x86/include/asm/smap.h b/arch/x86/include/asm/smap.h index 2b4ad4c6a226..3b5b2cf58dc6 100644 --- a/arch/x86/include/asm/smap.h +++ b/arch/x86/include/asm/smap.h @@ -35,7 +35,14 @@ * this directs the cpu to speculate with a NULL ptr rather than * something targeting kernel memory. * - * assumes CF is set from a previous 'cmp TASK_addr_limit, %ptr' + * In the syscall entry path it is possible to speculate past the + * validation of the system call number. Use MASK_NOSPEC to sanitize the + * syscall array index to zero (sys_read) rather than an arbitrary + * target. + * + * assumes CF is set from a previous 'cmp' i.e.: + * cmp TASK_addr_limit, %ptr + * cmp __NR_syscall_max, %idx */ .macro MASK_NOSPEC mask val sbb \mask, \mask
WARNING: multiple messages have this Message-ID (diff)
From: Dan Williams <dan.j.williams@intel.com> To: linux-kernel@vger.kernel.org Cc: linux-arch@vger.kernel.org, kernel-hardening@lists.openwall.com, gregkh@linuxfoundation.org, x86@kernel.org, Ingo Molnar <mingo@redhat.com>, Andy Lutomirski <luto@kernel.org>, "H. Peter Anvin" <hpa@zytor.com>, tglx@linutronix.de, torvalds@linux-foundation.org, akpm@linux-foundation.org, alan@linux.intel.com Subject: [kernel-hardening] [PATCH v4 07/10] x86: narrow out of bounds syscalls to sys_read under speculation Date: Thu, 18 Jan 2018 16:02:21 -0800 [thread overview] Message-ID: <151632014097.21271.16980532033566583357.stgit@dwillia2-desk3.amr.corp.intel.com> (raw) In-Reply-To: <151632009605.21271.11304291057104672116.stgit@dwillia2-desk3.amr.corp.intel.com> The syscall table base is a user controlled function pointer in kernel space. Like, 'get_user, use 'MASK_NOSPEC' to prevent any out of bounds speculation. While retpoline prevents speculating into the user controlled target it does not stop the pointer de-reference, the concern is leaking memory relative to the syscall table base. Reported-by: Linus Torvalds <torvalds@linux-foundation.org> Cc: Thomas Gleixner <tglx@linutronix.de> Cc: Ingo Molnar <mingo@redhat.com> Cc: "H. Peter Anvin" <hpa@zytor.com> Cc: x86@kernel.org Cc: Andy Lutomirski <luto@kernel.org> Signed-off-by: Dan Williams <dan.j.williams@intel.com> --- arch/x86/entry/entry_64.S | 2 ++ arch/x86/include/asm/smap.h | 9 ++++++++- 2 files changed, 10 insertions(+), 1 deletion(-) diff --git a/arch/x86/entry/entry_64.S b/arch/x86/entry/entry_64.S index 4f8e1d35a97c..2320017077d4 100644 --- a/arch/x86/entry/entry_64.S +++ b/arch/x86/entry/entry_64.S @@ -35,6 +35,7 @@ #include <asm/asm.h> #include <asm/smap.h> #include <asm/pgtable_types.h> +#include <asm/smap.h> #include <asm/export.h> #include <asm/frame.h> #include <asm/nospec-branch.h> @@ -264,6 +265,7 @@ entry_SYSCALL_64_fastpath: cmpl $__NR_syscall_max, %eax #endif ja 1f /* return -ENOSYS (already in pt_regs->ax) */ + MASK_NOSPEC %r11 %rax /* sanitize syscall_nr wrt speculation */ movq %r10, %rcx /* diff --git a/arch/x86/include/asm/smap.h b/arch/x86/include/asm/smap.h index 2b4ad4c6a226..3b5b2cf58dc6 100644 --- a/arch/x86/include/asm/smap.h +++ b/arch/x86/include/asm/smap.h @@ -35,7 +35,14 @@ * this directs the cpu to speculate with a NULL ptr rather than * something targeting kernel memory. * - * assumes CF is set from a previous 'cmp TASK_addr_limit, %ptr' + * In the syscall entry path it is possible to speculate past the + * validation of the system call number. Use MASK_NOSPEC to sanitize the + * syscall array index to zero (sys_read) rather than an arbitrary + * target. + * + * assumes CF is set from a previous 'cmp' i.e.: + * cmp TASK_addr_limit, %ptr + * cmp __NR_syscall_max, %idx */ .macro MASK_NOSPEC mask val sbb \mask, \mask
next prev parent reply other threads:[~2018-01-19 0:02 UTC|newest] Thread overview: 70+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-01-19 0:01 [PATCH v4 00/10] prevent bounds-check bypass via speculative execution Dan Williams 2018-01-19 0:01 ` [kernel-hardening] " Dan Williams 2018-01-19 0:01 ` Dan Williams 2018-01-19 0:01 ` [PATCH v4 01/10] Documentation: document array_ptr Dan Williams 2018-01-19 0:01 ` [kernel-hardening] " Dan Williams 2018-01-19 0:01 ` [PATCH v4 02/10] asm/nospec, array_ptr: sanitize speculative array de-references Dan Williams 2018-01-19 0:01 ` [kernel-hardening] " Dan Williams 2018-01-19 10:20 ` Jann Horn 2018-01-19 17:48 ` Adam Sampson 2018-01-19 17:48 ` Adam Sampson 2018-01-19 17:48 ` Adam Sampson 2018-01-19 17:48 ` Adam Sampson 2018-01-19 18:12 ` Dan Williams 2018-01-19 18:18 ` Will Deacon 2018-01-19 18:18 ` Will Deacon 2018-01-19 18:26 ` [kernel-hardening] " Dan Williams 2018-01-19 18:18 ` Linus Torvalds 2018-01-19 18:18 ` Linus Torvalds 2018-01-19 20:55 ` [kernel-hardening] " Dan Williams 2018-01-25 7:09 ` Cyril Novikov 2018-01-25 7:09 ` [kernel-hardening] " Cyril Novikov 2018-01-25 22:37 ` Dan Williams 2018-01-25 22:37 ` [kernel-hardening] " Dan Williams 2018-01-19 0:01 ` [PATCH v4 03/10] x86: implement array_ptr_mask() Dan Williams 2018-01-19 0:01 ` [kernel-hardening] " Dan Williams 2018-01-19 0:01 ` [PATCH v4 04/10] x86: introduce __uaccess_begin_nospec and ifence Dan Williams 2018-01-19 0:01 ` [kernel-hardening] " Dan Williams 2018-01-19 0:02 ` [PATCH v4 05/10] x86, __get_user: use __uaccess_begin_nospec Dan Williams 2018-01-19 0:02 ` [kernel-hardening] " Dan Williams 2018-01-19 0:02 ` [PATCH v4 06/10] x86, get_user: use pointer masking to limit speculation Dan Williams 2018-01-19 0:02 ` [kernel-hardening] " Dan Williams 2018-01-19 0:02 ` Dan Williams [this message] 2018-01-19 0:02 ` [kernel-hardening] [PATCH v4 07/10] x86: narrow out of bounds syscalls to sys_read under speculation Dan Williams 2018-01-24 14:40 ` Jiri Slaby 2018-01-24 14:40 ` [kernel-hardening] " Jiri Slaby 2018-02-06 19:29 ` Luis Henriques 2018-02-06 19:48 ` Dan Williams 2018-02-06 20:26 ` Linus Torvalds 2018-02-06 20:37 ` Dan Williams 2018-02-06 20:42 ` Linus Torvalds 2018-02-06 20:43 ` Linus Torvalds 2018-02-06 20:49 ` Andy Lutomirski 2018-02-06 20:58 ` Linus Torvalds 2018-02-06 21:37 ` Dan Williams 2018-02-06 22:52 ` Linus Torvalds 2018-02-07 0:33 ` Dan Williams 2018-02-07 1:23 ` Linus Torvalds 2018-02-06 22:51 ` Luis Henriques 2018-02-06 22:51 ` Luis Henriques 2018-01-19 0:02 ` [PATCH v4 08/10] vfs, fdtable: prevent bounds-check bypass via speculative execution Dan Williams 2018-01-19 0:02 ` [kernel-hardening] " Dan Williams 2018-01-19 0:02 ` [PATCH v4 09/10] kvm, x86: fix spectre-v1 mitigation Dan Williams 2018-01-19 0:02 ` [kernel-hardening] " Dan Williams 2018-01-19 8:42 ` Paolo Bonzini 2018-01-19 8:42 ` [kernel-hardening] " Paolo Bonzini 2018-01-19 0:02 ` [PATCH v4 10/10] nl80211: sanitize array index in parse_txq_params Dan Williams 2018-01-19 0:02 ` [kernel-hardening] " Dan Williams 2018-01-19 0:02 ` Dan Williams 2018-01-21 10:37 ` Johannes Berg 2018-01-21 10:37 ` [kernel-hardening] " Johannes Berg 2018-01-21 10:37 ` Johannes Berg 2018-01-20 6:58 ` [PATCH v4 00/10] prevent bounds-check bypass via speculative execution Dan Williams 2018-01-20 6:58 ` [kernel-hardening] " Dan Williams 2018-01-20 6:58 ` Dan Williams 2018-01-20 16:56 ` Alexei Starovoitov 2018-01-20 16:56 ` [kernel-hardening] " Alexei Starovoitov 2018-01-20 16:56 ` Alexei Starovoitov 2018-01-20 17:07 ` Alexei Starovoitov 2018-01-20 17:07 ` [kernel-hardening] " Alexei Starovoitov 2018-01-20 17:07 ` Alexei Starovoitov
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=151632014097.21271.16980532033566583357.stgit@dwillia2-desk3.amr.corp.intel.com \ --to=dan.j.williams@intel.com \ --cc=akpm@linux-foundation.org \ --cc=alan@linux.intel.com \ --cc=gregkh@linuxfoundation.org \ --cc=hpa@zytor.com \ --cc=kernel-hardening@lists.openwall.com \ --cc=linux-arch@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=luto@kernel.org \ --cc=mingo@redhat.com \ --cc=tglx@linutronix.de \ --cc=torvalds@linux-foundation.org \ --cc=x86@kernel.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: linkBe 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.