From: Hagar Hemdan <hagarhem@amazon.com>
To: Kent Gibson <warthog618@gmail.com>
Cc: Norbert Manthey <nmanthey@amazon.de>,
Linus Walleij <linus.walleij@linaro.org>,
Bartosz Golaszewski <brgl@bgdev.pl>, <linux-gpio@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <hagarhem@amazon.de>
Subject: Re: [PATCH v3] gpio: prevent potential speculation leaks in gpio_device_get_desc()
Date: Thu, 23 May 2024 08:18:43 +0000 [thread overview]
Message-ID: <20240523081843.GA7085@amazon.com> (raw)
In-Reply-To: <20240517124911.GA435070@rigel>
On Fri, May 17, 2024 at 08:49:11PM +0800, Kent Gibson wrote:
> On Fri, May 17, 2024 at 10:12:27AM +0000, Hagar Hemdan wrote:
> > Userspace may trigger a speculative read of an address outside the gpio
> > descriptor array.
> > Users can do that by calling gpio_ioctl() with an offset out of range.
> > Offset is copied from user and then used as an array index to get
> > the gpio descriptor without sanitization in gpio_device_get_desc().
> >
> > This change ensures that the offset is sanitized by using
> > array_index_nospec() to mitigate any possibility of speculative
> > information leaks.
> >
> > This bug was discovered and resolved using Coverity Static Analysis
> > Security Testing (SAST) by Synopsys, Inc.
> >
> > Fixes: aad955842d1c ("gpiolib: cdev: support GPIO_V2_GET_LINEINFO_IOCTL and GPIO_V2_GET_LINEINFO_WATCH_IOCTL")
>
> I still don't think this Fixes commit is right, and that would impact
> where this gets backported to, but Bart can weigh in on that.
>
> Cheers,
> Kent.
>
yes, this Fixes commit is wrong. Stable trees need another fix patch.
I will remove this Fixes commit in the next revision.
Thanks,
Hagar
>
> > Signed-off-by: Hagar Hemdan <hagarhem@amazon.com>
> > ---
> > v3: update the commit mesg
> > ---
> > drivers/gpio/gpiolib.c | 3 ++-
> > 1 file changed, 2 insertions(+), 1 deletion(-)
> >
> > diff --git a/drivers/gpio/gpiolib.c b/drivers/gpio/gpiolib.c
> > index fa50db0c3605..b58e4fe78cec 100644
> > --- a/drivers/gpio/gpiolib.c
> > +++ b/drivers/gpio/gpiolib.c
> > @@ -17,6 +17,7 @@
> > #include <linux/list.h>
> > #include <linux/lockdep.h>
> > #include <linux/module.h>
> > +#include <linux/nospec.h>
> > #include <linux/of.h>
> > #include <linux/pinctrl/consumer.h>
> > #include <linux/seq_file.h>
> > @@ -201,7 +202,7 @@ gpio_device_get_desc(struct gpio_device *gdev, unsigned int hwnum)
> > if (hwnum >= gdev->ngpio)
> > return ERR_PTR(-EINVAL);
> >
> > - return &gdev->descs[hwnum];
> > + return &gdev->descs[array_index_nospec(hwnum, gdev->ngpio)];
> > }
> > EXPORT_SYMBOL_GPL(gpio_device_get_desc);
> >
> > --
> > 2.40.1
> >
prev parent reply other threads:[~2024-05-23 8:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-17 10:12 [PATCH v3] gpio: prevent potential speculation leaks in gpio_device_get_desc() Hagar Hemdan
2024-05-17 12:49 ` Kent Gibson
2024-05-23 8:18 ` Hagar Hemdan [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=20240523081843.GA7085@amazon.com \
--to=hagarhem@amazon.com \
--cc=brgl@bgdev.pl \
--cc=hagarhem@amazon.de \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nmanthey@amazon.de \
--cc=warthog618@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