mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Dianzhang Chen <dianzhangchen0@gmail.com>
Cc: oleg@redhat.com, mingo@redhat.com, bp@alien8.de, hpa@zytor.com,
	x86@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86: fix possible spectre-v1 in ptrace_get_debugreg()
Date: Sun, 23 Jun 2019 13:52:51 +0200 (CEST)	[thread overview]
Message-ID: <alpine.DEB.2.21.1906231348340.32342@nanos.tec.linutronix.de> (raw)
In-Reply-To: <1558702622-15143-1-git-send-email-dianzhangchen0@gmail.com>

On Fri, 24 May 2019, Dianzhang Chen wrote:

> Subject : [PATCH] x86: fix possible spectre-v1 in ptrace_get_debugreg()

Please use the proper prefix. Run git log on the file and you'll find
it. Also please start the short summary sentence after the prefix with an
upper case letter.

> The n in ptrace_get_debugreg() is indirectly controlled by userspace via syscall: ptrace(defined in kernel/ptrace.c), hence leading to a potential exploitation of the Spectre variant 1 vulnerability.
> The n can be controlled from: ptrace -> arch_ptrace -> ptrace_get_debugreg.
>

Please format the text proper with a line break around column 70.

Also please refrain from '(defined in kernel/ptrace.c)'. Use sys_ptrace()
which is entirely clear.

> Fix this by sanitizing n before using it to index thread->ptrace_bps.
> 
> Signed-off-by: Dianzhang Chen <dianzhangchen0@gmail.com>
> ---
>  arch/x86/kernel/ptrace.c | 4 +++-
>  1 file changed, 3 insertions(+), 1 deletion(-)
> 
> diff --git a/arch/x86/kernel/ptrace.c b/arch/x86/kernel/ptrace.c
> index 4b8ee05..3f8f158 100644
> --- a/arch/x86/kernel/ptrace.c
> +++ b/arch/x86/kernel/ptrace.c
> @@ -24,6 +24,7 @@
>  #include <linux/rcupdate.h>
>  #include <linux/export.h>
>  #include <linux/context_tracking.h>
> +#include <linux/nospec.h>
>  
>  #include <linux/uaccess.h>
>  #include <asm/pgtable.h>
> @@ -644,7 +645,8 @@ static unsigned long ptrace_get_debugreg(struct task_struct *tsk, int n)
>  	unsigned long val = 0;
>  
>  	if (n < HBP_NUM) {
> -		struct perf_event *bp = thread->ptrace_bps[n];
> +		struct perf_event *bp =
> +			thread->ptrace_bps[array_index_nospec(n, HBP_NUM)];

Please use an intermediate variable to calculate the index instead of this
weird line break.

Thanks,

	tglx

      reply	other threads:[~2019-06-23 11:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-24 12:57 Dianzhang Chen
2019-06-23 11:52 ` Thomas Gleixner [this message]

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.21.1906231348340.32342@nanos.tec.linutronix.de \
    --to=tglx@linutronix.de \
    --cc=bp@alien8.de \
    --cc=dianzhangchen0@gmail.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=oleg@redhat.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®