From: Thomas Gleixner <tglx@linutronix.de>
To: Andy Lutomirski <luto@amacapital.net>
Cc: x86@kernel.org, linux-kernel@vger.kernel.org,
Dave Hansen <dave.hansen@linux.intel.com>,
Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
Subject: Re: [PATCH 3.19 v4 1/2] x86, mpx: Short-circuit the instruction decoder for unexpected opcodes
Date: Tue, 20 Jan 2015 14:59:16 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.11.1501201450220.5526@nanos> (raw)
In-Reply-To: <44852495d71796ecf690208e2e908a1b25008a73.1421183147.git.luto@amacapital.net>
On Tue, 13 Jan 2015, Andy Lutomirski wrote:
> This reduces the degree to which we're exposing the instruction decoder
> to malicious user code at very little complexity cost.
>
> Signed-off-by: Andy Lutomirski <luto@amacapital.net>
> ---
> arch/x86/mm/mpx.c | 25 ++++++++++++++++---------
> 1 file changed, 16 insertions(+), 9 deletions(-)
>
> diff --git a/arch/x86/mm/mpx.c b/arch/x86/mm/mpx.c
> index 67ebf5751222..a73004330732 100644
> --- a/arch/x86/mm/mpx.c
> +++ b/arch/x86/mm/mpx.c
> @@ -230,6 +230,22 @@ static int mpx_insn_decode(struct insn *insn,
> */
> if (!nr_copied)
> return -EFAULT;
> +
> + /*
> + * We only _really_ need to decode bndcl/bndcn/bndcu
> + * Error out on anything else. Check this before decoding the
> + * instruction to reduce our exposure to intentionally bad code
> + * to some extent. Note that this shortcut can incorrectly return
> + * -EINVAL instead of -EFAULT under some circumstances. This
> + * discrepancy has no effect.
> + */
> + if (nr_copied < 2)
> + goto bad_opcode;
> + if (buf[0] != 0x0f)
> + goto bad_opcode;
> + if (buf[1] != 0x1a && buf[1] != 0x1b)
> + goto bad_opcode;
These opcodes can never have a prefix? If so, then we want to add this
to the comment.
Thanks,
tglx
next prev parent reply other threads:[~2015-01-20 13:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-13 21:49 [PATCH 3.19 v4 0/2] x86, mpx: Instruction decoder fixes and hardening Andy Lutomirski
2015-01-13 21:49 ` [PATCH 3.19 v4 1/2] x86, mpx: Short-circuit the instruction decoder for unexpected opcodes Andy Lutomirski
2015-01-20 13:59 ` Thomas Gleixner [this message]
2015-01-20 22:28 ` Andy Lutomirski
2015-01-13 21:49 ` [PATCH 3.19 v4 2/2] x86: Enforce maximum instruction size in the instruction decoder Andy Lutomirski
2015-01-15 12:37 ` Masami Hiramatsu
2015-01-15 15:22 ` Andy Lutomirski
2015-01-16 1:02 ` Masami Hiramatsu
2015-01-27 23:56 ` Andy Lutomirski
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=alpine.DEB.2.11.1501201450220.5526@nanos \
--to=tglx@linutronix.de \
--cc=dave.hansen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=masami.hiramatsu.pt@hitachi.com \
--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®