From: Thomas Hellstrom <thellstrom@vmware.com>
To: Deepak Singh Rawat <drawat@vmware.com>,
"Gustavo A. R. Silva" <gustavo@embeddedor.com>,
linux-graphics-maintainer <linux-graphics-maintainer@vmware.com>,
Sinclair Yeh <syeh@vmware.com>, David Airlie <airlied@linux.ie>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>
Subject: Re: [Linux-graphics-maintainer] [PATCH] drm/vmwgfx: Fix potential Spectre v1
Date: Tue, 21 Aug 2018 10:19:16 +0200 [thread overview]
Message-ID: <68b1a4bc-87d8-a93a-edd1-5794ca9e93f6@vmware.com> (raw)
In-Reply-To: <BYAPR05MB41817986B00F59780A68D63CBA320@BYAPR05MB4181.namprd05.prod.outlook.com>
On 08/20/2018 10:53 PM, Deepak Singh Rawat wrote:
> Looks good to me based on my limited understanding. Thomas/Sinclair can
> could you please review and then we can include this in drm-fixes.
>
> Thanks,
> Deepak
>
>> arg.version is indirectly controlled by user-space, hence leading to
>> a potential exploitation of the Spectre variant 1 vulnerability.
>>
>> This issue was detected with the help of Smatch:
>>
>> drivers/gpu/drm/vmwgfx/vmwgfx_execbuf.c:4526 vmw_execbuf_ioctl()
>> warn:
>> potential spectre issue 'copy_offset' [w]
>>
>> Fix this by sanitizing arg.version before using it to index copy_offset
>>
>> Notice that given that speculation windows are large, the policy is
>> to kill the speculation on the first load and not worry if it can be
>> completed with a dependent load/store [1].
>>
>> [1]
>>
>>
>> Cc: stable@vger.kernel.org
>> Signed-off-by: Gustavo A. R. Silva <gustavo@embeddedor.com>
>> ---
>> drivers/gpu/drm/vmwgfx/vmwgfx_execbuf.c | 7 +++++--
>> 1 file changed, 5 insertions(+), 2 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/vmwgfx/vmwgfx_execbuf.c
>> b/drivers/gpu/drm/vmwgfx/vmwgfx_execbuf.c
>> index 1f13457..ad91c6e 100644
>> --- a/drivers/gpu/drm/vmwgfx/vmwgfx_execbuf.c
>> +++ b/drivers/gpu/drm/vmwgfx/vmwgfx_execbuf.c
>> @@ -25,6 +25,7 @@
>> *
>>
>> **********************************************************
>> ****************/
>> #include <linux/sync_file.h>
>> +#include <linux/nospec.h>
>>
>> #include "vmwgfx_drv.h"
>> #include "vmwgfx_reg.h"
>> @@ -4520,8 +4521,10 @@ int vmw_execbuf_ioctl(struct drm_device *dev,
>> unsigned long data,
>> return -EINVAL;
>> }
>>
>> - if (arg.version > 1 &&
>> - copy_from_user(&arg.context_handle,
>> + if (arg.version >= ARRAY_SIZE(copy_offset))
>> + return -EFAULT;
I must admit my understanding of spectre workings in this case is
limited, but why do you need to compare
arg.version against ARRAY_SIZE here, when it is already checked against
DRM_VMW_EXECBUF_VERSION earlier?
>> + arg.version = array_index_nospec(arg.version,
>> ARRAY_SIZE(copy_offset));
>> + if (copy_from_user(&arg.context_handle,
>> (void __user *) (data + copy_offset[0]),
>> copy_offset[arg.version - 1] -
>> copy_offset[0]) != 0)
Similarly, we want to perform this copy iff arg.version > 1. Why did you
remove that check?
Thanks,
Thomas
>> --
>> 2.7.4
>>
>> _______________________________________________
>> Sent to linux-graphics-maintainer@vmware.com
next prev parent reply other threads:[~2018-08-21 8:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-16 19:30 Gustavo A. R. Silva
2018-08-20 20:53 ` [Linux-graphics-maintainer] " Deepak Singh Rawat
2018-08-21 8:19 ` Thomas Hellstrom [this message]
2018-08-23 14:43 ` Gustavo A. R. Silva
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=68b1a4bc-87d8-a93a-edd1-5794ca9e93f6@vmware.com \
--to=thellstrom@vmware.com \
--cc=airlied@linux.ie \
--cc=drawat@vmware.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=gustavo@embeddedor.com \
--cc=linux-graphics-maintainer@vmware.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syeh@vmware.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
all inboxes | Powered by JetHome®