mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Gustavo A. R. Silva" <gustavo@embeddedor.com>
To: Jinbum Park <jinb.park7@gmail.com>,
	axboe@kernel.dk, bart.vanassche@wdc.com,
	jiufei.xue@linux.alibaba.com
Cc: linux-block@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] pktcdvd: Fix possible Spectre-v1 for pkt_devs
Date: Fri, 27 Jul 2018 21:56:38 -0500	[thread overview]
Message-ID: <d46d997c-e0c1-a77b-a234-3f9d39d9a5b8@embeddedor.com> (raw)
In-Reply-To: <0f94623c-47e2-31e6-50ac-1d11ba061411@embeddedor.com>

Jinbum,

I just noticed this patch does not apply to linux-next.

Please try again, but this time work from linux-next rather than from a stable tree.

Thanks
--
Gustavo

On 07/27/2018 09:47 PM, Gustavo A. R. Silva wrote:
> 
> 
> On 07/27/2018 09:30 PM, Jinbum Park wrote:
>> User controls @dev_minor which to be used as index of pkt_devs.
>> So, It can be exploited via Spectre-like attack. (speculative execution)
>>
>> This kind of attack leaks address of pkt_devs, [1]
>> It leads an attacker to bypass security mechanism such as KASLR.
>>
>> So sanitize @dev_minor before using it to prevent attack.
>>
>> [1] https://github.com/jinb-park/linux-exploit/
>> tree/master/exploit-remaining-spectre-gadget/leak_pkt_devs.c
>>
>> Signed-off-by: Jinbum Park <jinb.park7@gmail.com>
>> ---
>> v2: Fix coding style by Gustavo.
>>
>>  drivers/block/pktcdvd.c | 3 ++-
>>  1 file changed, 2 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/block/pktcdvd.c b/drivers/block/pktcdvd.c
>> index c61d20c..8ec2eaa 100644
>> --- a/drivers/block/pktcdvd.c
>> +++ b/drivers/block/pktcdvd.c
>> @@ -67,8 +67,8 @@
>>  #include <scsi/scsi.h>
>>  #include <linux/debugfs.h>
>>  #include <linux/device.h>
>> -
>>  #include <linux/uaccess.h>
>> +#include <linux/nospec.h>
>>  
>>  #define DRIVER_NAME	"pktcdvd"
>>  
>> @@ -2231,6 +2231,7 @@ static struct pktcdvd_device *pkt_find_dev_from_minor(unsigned int dev_minor)
>>  {
>>  	if (dev_minor >= MAX_WRITERS)
>>  		return NULL;
>> +	dev_minor = array_index_nospec(dev_minor, MAX_WRITERS);
> 
> Adding a blank line here would be even better.
> 
>>  	return pkt_devs[dev_minor];
>>  }
>>  
>>
> 
> Acked-by: Gustavo A. R. Silva <gustavo@embeddedor.com>
> 
> Thanks
> --
> Gustavo
> 

      reply	other threads:[~2018-07-28  3:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-28  2:30 Jinbum Park
2018-07-28  2:47 ` Gustavo A. R. Silva
2018-07-28  2:56   ` Gustavo A. R. Silva [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=d46d997c-e0c1-a77b-a234-3f9d39d9a5b8@embeddedor.com \
    --to=gustavo@embeddedor.com \
    --cc=axboe@kernel.dk \
    --cc=bart.vanassche@wdc.com \
    --cc=jinb.park7@gmail.com \
    --cc=jiufei.xue@linux.alibaba.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®