[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.11.1501201450220.5526@nanos>
Date: Tue, 20 Jan 2015 14:59:16 +0100 (CET)
From: Thomas Gleixner <tglx@...utronix.de>
To: Andy Lutomirski <luto@...capital.net>
cc: x86@...nel.org, linux-kernel@...r.kernel.org,
Dave Hansen <dave.hansen@...ux.intel.com>,
Masami Hiramatsu <masami.hiramatsu.pt@...achi.com>
Subject: Re: [PATCH 3.19 v4 1/2] x86, mpx: Short-circuit the instruction
decoder for unexpected opcodes
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@...capital.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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists