From: Andy Lutomirski <luto@kernel.org>
To: x86@kernel.org
Cc: Borislav Petkov <bp@alien8.de>,
linux-kernel@vger.kernel.org, Andy Lutomirski <luto@kernel.org>
Subject: [PATCH] x86/entry/32: Add an ASM_CLAC to entry_SYSENTER_32
Date: Tue, 23 Feb 2016 13:19:29 -0800 [thread overview]
Message-ID: <3e36be110724896e32a4a1fe73bacb349d3cba94.1456262295.git.luto@kernel.org> (raw)
Both before and after 5f310f739b4c ("x86/entry/32: Re-implement
SYSENTER using the new C path"), we relied on a uaccess very early
in the SYSENTER path to clear AC. After that change, though, we can
potentially make it all the way into C code with AC set, which
enlarges the attack surface for SMAP bypass by doing SYSENTER with
AC set.
Strengthen the SMAP protection by addding the missing ASM_CLAC right
at the beginning.
Signed-off-by: Andy Lutomirski <luto@kernel.org>
---
This is probably an x86/urgent candidate. It fixes a minor
hardening regression in 4.4.
It's lightly tested. It's hard to test well right now because the
4.5 series is completely broken for 32-bit SMAP sytems.
arch/x86/entry/entry_32.S | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/x86/entry/entry_32.S b/arch/x86/entry/entry_32.S
index f3facd40fd2d..9d6165c171eb 100644
--- a/arch/x86/entry/entry_32.S
+++ b/arch/x86/entry/entry_32.S
@@ -294,6 +294,7 @@ sysenter_past_esp:
pushl $__USER_DS /* pt_regs->ss */
pushl %ebp /* pt_regs->sp (stashed in bp) */
pushfl /* pt_regs->flags (except IF = 0) */
+ ASM_CLAC /* Clear AC after saving FLAGS */
orl $X86_EFLAGS_IF, (%esp) /* Fix IF */
pushl $__USER_CS /* pt_regs->cs */
pushl $0 /* pt_regs->ip = 0 (placeholder) */
--
2.5.0
next reply other threads:[~2016-02-23 21:19 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-23 21:19 Andy Lutomirski [this message]
2016-02-24 15:46 ` Brian Gerst
2016-02-24 16:56 ` Andy Lutomirski
2016-02-25 5:53 ` [tip:x86/urgent] " tip-bot for Andy Lutomirski
2016-02-25 6:00 ` H. Peter Anvin
2016-02-25 8:07 ` Andy Lutomirski
2016-02-25 8:11 ` Andy Lutomirski
2016-02-25 8:14 ` Ingo Molnar
2016-02-25 8:29 ` Mike Galbraith
2016-02-25 8:40 ` Ingo Molnar
2016-02-25 9:08 ` Mike Galbraith
[not found] ` <CALCETrWqCnhxvQ5qNp_O_7K7KW1H3FmHiX=mp+C5oeBEx=3YVA@mail.gmail.com>
2016-02-25 13:47 ` Brian Gerst
2016-02-25 15:42 ` Brian Gerst
2016-02-25 18:20 ` Andy Lutomirski
2016-02-25 18:30 ` Linus Torvalds
2016-02-25 18:40 ` Andy Lutomirski
2016-02-25 19:31 ` Brian Gerst
2016-02-25 19:39 ` Andy Lutomirski
2016-02-25 19:49 ` Brian Gerst
2016-02-25 19:52 ` Andy Lutomirski
2016-02-25 20:54 ` Linus Torvalds
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=3e36be110724896e32a4a1fe73bacb349d3cba94.1456262295.git.luto@kernel.org \
--to=luto@kernel.org \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.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: 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
all inboxes | Powered by JetHome®