Linux EDAC development
 help / color / mirror / Atom feed
From: "Luck, Tony" <tony.luck@intel.com>
To: Borislav Petkov <bp@alien8.de>
Cc: Dan Carpenter <dan.carpenter@oracle.com>, linux-edac@vger.kernel.org
Subject: Re: [bug report] x86/mce: Prevent severity computation from being instrumented
Date: Fri, 17 Dec 2021 09:13:39 -0800	[thread overview]
Message-ID: <YbzFQ40JUftkpeKi@agluck-desk2.amr.corp.intel.com> (raw)
In-Reply-To: <Ybx0qV3S61Hjj+jw@zn.tnic>

On Fri, Dec 17, 2021 at 12:29:45PM +0100, Borislav Petkov wrote:
> + Tony.
> 
> On Fri, Dec 17, 2021 at 01:20:29PM +0300, Dan Carpenter wrote:
> > Hello Borislav Petkov,
> > 
> > This is a semi-automatic email about new static checker warnings.
> > 
> > The patch 0a5b288e85bb: "x86/mce: Prevent severity computation from
> > being instrumented" from Oct 13, 2021, leads to the following Smatch
> > complaint:
> > 
> >     arch/x86/kernel/cpu/mce/severity.c:286 error_context()
> >     warn: variable dereferenced before check 'regs' (see line 280)
> > 
> > arch/x86/kernel/cpu/mce/severity.c
> >    279		fixup_type = ex_get_fixup_type(m->ip);
> >    280		copy_user  = is_copy_from_user(regs);
> >                                                ^^^^
> > New unchecked dereference
> > 
> >    281		instrumentation_end();
> >    282	
> >    283		switch (fixup_type) {
> >    284		case EX_TYPE_UACCESS:
> >    285		case EX_TYPE_COPY:
> >    286			if (!regs || !copy_user)
> >                              ^^^^
> > Old code checked for NULL
> > 
> >    287				return IN_KERNEL;
> >    288			m->kflags |= MCE_IN_KERNEL_COPYIN;
> 
> Good catch, thanks!
> 
> I guess we can do something like this:
> 
> ---
> diff --git a/arch/x86/kernel/cpu/mce/severity.c b/arch/x86/kernel/cpu/mce/severity.c
> index a32646769705..7aa2bda93cbb 100644
> --- a/arch/x86/kernel/cpu/mce/severity.c
> +++ b/arch/x86/kernel/cpu/mce/severity.c
> @@ -222,6 +222,9 @@ static bool is_copy_from_user(struct pt_regs *regs)
>  	struct insn insn;
>  	int ret;
>  
> +	if (!regs)
> +		return false;
> +
>  	if (copy_from_kernel_nofault(insn_buf, (void *)regs->ip, MAX_INSN_SIZE))
>  		return false;
>  
> @@ -283,7 +286,7 @@ static noinstr int error_context(struct mce *m, struct pt_regs *regs)
>  	switch (fixup_type) {
>  	case EX_TYPE_UACCESS:
>  	case EX_TYPE_COPY:
> -		if (!regs || !copy_user)
> +		if (!copy_user)
>  			return IN_KERNEL;
>  		m->kflags |= MCE_IN_KERNEL_COPYIN;
>  		fallthrough;
> 

Looks good to me.

Reviewed-by: Tony Luck <tony.luck@intel.com>

-Tony

  reply	other threads:[~2021-12-17 17:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-17 10:20 [bug report] x86/mce: Prevent severity computation from being instrumented Dan Carpenter
2021-12-17 11:29 ` Borislav Petkov
2021-12-17 17:13   ` Luck, Tony [this message]
2021-12-17 23:50     ` [PATCH] x86/mce: Check regs before accessing it Borislav Petkov

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=YbzFQ40JUftkpeKi@agluck-desk2.amr.corp.intel.com \
    --to=tony.luck@intel.com \
    --cc=bp@alien8.de \
    --cc=dan.carpenter@oracle.com \
    --cc=linux-edac@vger.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