From: Kent Gibson <warthog618@gmail.com>
To: Bartosz Golaszewski <brgl@bgdev.pl>
Cc: Linus Walleij <linus.walleij@linaro.org>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
Subject: Re: [PATCH] gpiolib: cdev: fix NULL-pointer dereferences
Date: Sat, 26 Nov 2022 00:24:47 +0800 [thread overview]
Message-ID: <Y4DsTxPH1tv5eEwf@sol> (raw)
In-Reply-To: <20221125153257.528826-1-brgl@bgdev.pl>
On Fri, Nov 25, 2022 at 04:32:57PM +0100, Bartosz Golaszewski wrote:
> From: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
>
> There are several places where we can crash the kernel by requesting
> lines, unbinding the GPIO device, then calling any of the system calls
> relevant to the GPIO character device's annonymous file descriptors:
> ioctl(), read(), poll().
>
> While I observed it with the GPIO simulator, it will also happen for any
> of the GPIO devices that can be hot-unplugged - for instance any HID GPIO
> expander (e.g. CP2112).
>
> This affects both v1 and v2 uAPI.
>
> Fix this by simply checking if the GPIO chip pointer is not NULL.
>
Fixes: ??
And split for v1 and v2 as the Fixes for those will differ?
> Signed-off-by: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
> ---
> drivers/gpio/gpiolib-cdev.c | 15 +++++++++++++++
> 1 file changed, 15 insertions(+)
>
> diff --git a/drivers/gpio/gpiolib-cdev.c b/drivers/gpio/gpiolib-cdev.c
> index 0cb6b468f364..d5632742942a 100644
> --- a/drivers/gpio/gpiolib-cdev.c
> +++ b/drivers/gpio/gpiolib-cdev.c
> @@ -201,6 +201,9 @@ static long linehandle_ioctl(struct file *file, unsigned int cmd,
> unsigned int i;
> int ret;
>
> + if (!lh->gdev->chip)
> + return -ENODEV;
> +
Is there anything to prevent the chip being removed by another thread
between this check and subsequent usage?
Cheers,
Kent.
> switch (cmd) {
> case GPIOHANDLE_GET_LINE_VALUES_IOCTL:
> /* NOTE: It's okay to read values of output lines */
> @@ -1384,6 +1387,9 @@ static long linereq_ioctl(struct file *file, unsigned int cmd,
> struct linereq *lr = file->private_data;
> void __user *ip = (void __user *)arg;
>
> + if (!lr->gdev->chip)
> + return -ENODEV;
> +
> switch (cmd) {
> case GPIO_V2_LINE_GET_VALUES_IOCTL:
> return linereq_get_values(lr, ip);
> @@ -1716,6 +1722,9 @@ static __poll_t lineevent_poll(struct file *file,
> struct lineevent_state *le = file->private_data;
> __poll_t events = 0;
>
> + if (!le->gdev->chip)
> + return -ENODEV;
> +
> poll_wait(file, &le->wait, wait);
>
> if (!kfifo_is_empty_spinlocked_noirqsave(&le->events, &le->wait.lock))
> @@ -1740,6 +1749,9 @@ static ssize_t lineevent_read(struct file *file,
> ssize_t ge_size;
> int ret;
>
> + if (!le->gdev->chip)
> + return -ENODEV;
> +
> /*
> * When compatible system call is being used the struct gpioevent_data,
> * in case of at least ia32, has different size due to the alignment
> @@ -1821,6 +1833,9 @@ static long lineevent_ioctl(struct file *file, unsigned int cmd,
> void __user *ip = (void __user *)arg;
> struct gpiohandle_data ghd;
>
> + if (!le->gdev->chip)
> + return -ENODEV;
> +
> /*
> * We can get the value for an event line but not set it,
> * because it is input by definition.
> --
> 2.37.2
>
next prev parent reply other threads:[~2022-11-25 16:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-25 15:32 [PATCH] gpiolib: cdev: fix NULL-pointer dereferences Bartosz Golaszewski
2022-11-25 16:24 ` Kent Gibson [this message]
2022-11-25 16:48 ` Bartosz Golaszewski
2022-11-25 17:56 ` Andy Shevchenko
2022-11-25 18:02 ` Andy Shevchenko
2022-11-25 21:03 ` Bartosz Golaszewski
2022-11-25 21:33 ` Andy Shevchenko
2022-11-26 0:39 ` Kent Gibson
2022-11-26 4:02 ` kernel test robot
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=Y4DsTxPH1tv5eEwf@sol \
--to=warthog618@gmail.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=bartosz.golaszewski@linaro.org \
--cc=brgl@bgdev.pl \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@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;
as well as URLs for NNTP newsgroup(s).