Linux GPIO subsystem development
 help / color / mirror / Atom feed
From: Alexander Lobakin <aleksander.lobakin@intel.com>
To: Aleksandr Mishin <amishin@t-argos.ru>
Cc: Keerthy <j-keerthy@ti.com>,
	Linus Walleij <linus.walleij@linaro.org>,
	Bartosz Golaszewski <brgl@bgdev.pl>,
	"Andrew F. Davis" <afd@ti.com>, <linux-gpio@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>, <lvc-project@linuxtesting.org>
Subject: Re: [PATCH] gpio: davinci: Fix potential buffer overflow
Date: Thu, 28 Mar 2024 16:27:24 +0100	[thread overview]
Message-ID: <b2c6bc3e-11c5-4a20-8a30-666821ab2613@intel.com> (raw)
In-Reply-To: <20240328091021.18027-1-amishin@t-argos.ru>

From: Aleksandr Mishin <amishin@t-argos.ru>
Date: Thu, 28 Mar 2024 12:10:21 +0300

> In davinci_gpio_probe() accessing an element of array 'chips->regs' of size 5 and
> array 'offset_array' of size 5 can lead to a buffer overflow, since the index
> 'bank' can have an out of range value 63.
> Fix this bug by limiting top index value.
> 
> Found by Linux Verification Center (linuxtesting.org) with SVACE.
> 
> Fixes: c809e37a3b5a ("gpio: davinci: Allocate the correct amount of memory for controller")
> Signed-off-by: Aleksandr Mishin <amishin@t-argos.ru>
> ---
>  drivers/gpio/gpio-davinci.c | 3 +++
>  1 file changed, 3 insertions(+)
> 
> diff --git a/drivers/gpio/gpio-davinci.c b/drivers/gpio/gpio-davinci.c
> index bb499e362912..b65df1f2b83f 100644
> --- a/drivers/gpio/gpio-davinci.c
> +++ b/drivers/gpio/gpio-davinci.c
> @@ -257,6 +257,9 @@ static int davinci_gpio_probe(struct platform_device *pdev)
>  	spin_lock_init(&chips->lock);
>  
>  	nbank = DIV_ROUND_UP(ngpio, 32);
> +    if (nbank > MAX_REGS_BANKS || nbank > 5) {
> +        nbank = MAX_REGS_BANKS < 5 ? MAX_REGS_BANKS : 5;
> +	}

Static analysis warnings make no sense until you provide a reliable way
to trigger the problem on real systems.

>  	for (bank = 0; bank < nbank; bank++)
>  		chips->regs[bank] = gpio_base + offset_array[bank];
>  

Thanks,
Olek

  parent reply	other threads:[~2024-03-28 15:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-28  9:10 [PATCH] gpio: davinci: Fix potential buffer overflow Aleksandr Mishin
2024-03-28 10:32 ` Dan Carpenter
2024-03-28 15:27 ` Alexander Lobakin [this message]
2024-03-28 16:23   ` Aleksandr Mishin
2024-03-28 16:32     ` Alexander Lobakin
2024-03-28 16:45   ` Dan Carpenter

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=b2c6bc3e-11c5-4a20-8a30-666821ab2613@intel.com \
    --to=aleksander.lobakin@intel.com \
    --cc=afd@ti.com \
    --cc=amishin@t-argos.ru \
    --cc=brgl@bgdev.pl \
    --cc=j-keerthy@ti.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lvc-project@linuxtesting.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