public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Hari Prasath Gujulan Elango <Hari.PrasathGE@microchip.com>
Cc: alexandre.belloni@bootlin.com, richard.genoud@gmail.com,
	linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org,
	claudiu.beznea@tuxon.dev, jirislaby@kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] serial: atmel: Fix Spectre v1 vulnerability reported by smatch
Date: Tue, 22 Aug 2023 13:30:25 +0200	[thread overview]
Message-ID: <2023082220-matchless-stagnate-7dab@gregkh> (raw)
In-Reply-To: <20230822111321.56434-1-Hari.PrasathGE@microchip.com>

On Tue, Aug 22, 2023 at 04:43:21PM +0530, Hari Prasath Gujulan Elango wrote:
> smatch reports the below spectre variant 1 vulnerability.
> 
> drivers/tty/serial/atmel_serial.c:2675 atmel_console_setup() warn: potential spectre issue 'atmel_ports' [r] (local cap)
> 
> Fix the same by using the array_index_nospec() to mitigate this
> potential vulnerability especially because the console index is
> controlled by user-space.
> 
> Signed-off-by: Hari Prasath Gujulan Elango <Hari.PrasathGE@microchip.com>
> ---
>  drivers/tty/serial/atmel_serial.c | 15 +++++++++++++--
>  1 file changed, 13 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/tty/serial/atmel_serial.c b/drivers/tty/serial/atmel_serial.c
> index 3467a875641a..25f004dd9efd 100644
> --- a/drivers/tty/serial/atmel_serial.c
> +++ b/drivers/tty/serial/atmel_serial.c
> @@ -33,6 +33,7 @@
>  #include <linux/suspend.h>
>  #include <linux/mm.h>
>  #include <linux/io.h>
> +#include <linux/nospec.h>
>  
>  #include <asm/div64.h>
>  #include <asm/ioctls.h>
> @@ -2662,13 +2663,23 @@ static void __init atmel_console_get_options(struct uart_port *port, int *baud,
>  
>  static int __init atmel_console_setup(struct console *co, char *options)
>  {
> -	struct uart_port *port = &atmel_ports[co->index].uart;
> -	struct atmel_uart_port *atmel_port = to_atmel_uart_port(port);
> +	struct uart_port *port;
> +	struct atmel_uart_port *atmel_port;
>  	int baud = 115200;
>  	int bits = 8;
>  	int parity = 'n';
>  	int flow = 'n';
>  
> +	if (unlikely(co->index < 0 || co->index >= ATMEL_MAX_UART))

Only ever use likely/unlikely if you can measure the difference with and
without the marking.  Otherwise do not use it as the compiler and cpu do
a better job than we do in figuring this out.


> +		return -ENODEV;
> +
> +	co->index = array_index_nospec(co->index, ATMEL_MAX_UART);

How exactl is index controlled by userspace such that a spectre gadget
can be used here?  You have to be able to call this multiple times in a
row, unsuccessfully and successfully, how does that happen through the
console api?

thanks,

greg k-h

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

      reply	other threads:[~2023-08-22 11:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-22 11:13 [PATCH] serial: atmel: Fix Spectre v1 vulnerability reported by smatch Hari Prasath Gujulan Elango
2023-08-22 11:30 ` Greg KH [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=2023082220-matchless-stagnate-7dab@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=Hari.PrasathGE@microchip.com \
    --cc=alexandre.belloni@bootlin.com \
    --cc=claudiu.beznea@tuxon.dev \
    --cc=jirislaby@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=richard.genoud@gmail.com \
    /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