From: "Javier Carrasco" <javier.carrasco.cruz@gmail.com>
To: "Karan Sanghavi" <karansanghvi98@gmail.com>,
"Jonathan Cameron" <jic23@kernel.org>,
"Lars-Peter Clausen" <lars@metafoo.de>
Cc: <linux-iio@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
"Shuah Khan" <skhan@linuxfoundation.org>
Subject: Re: [PATCH v3] iio: light: Add check for array bounds in veml6075_read_int_time_ms
Date: Thu, 20 Feb 2025 21:00:40 +0100 [thread overview]
Message-ID: <D7XJGM6MAB6N.2FYSUN4OJELUA@gmail.com> (raw)
In-Reply-To: <Z7dnrEpKQdRZ2qFU@Emma>
On Thu Feb 20, 2025 at 6:34 PM CET, Karan Sanghavi wrote:
> The array contains only 5 elements, but the index calculated by
> veml6075_read_int_time_index can range from 0 to 7,
> which could lead to out-of-bounds access. The check prevents this issue.
>
> Coverity Issue
> CID 1574309: (#1 of 1): Out-of-bounds read (OVERRUN)
> overrun-local: Overrunning array veml6075_it_ms of 5 4-byte
> elements at element index 7 (byte offset 31) using
> index int_index (which evaluates to 7)
>
> Fixes: 3b82f43238ae ("iio: light: add VEML6075 UVA and UVB light sensor driver")
> Signed-off-by: Karan Sanghavi <karansanghvi98@gmail.com>
> ---
> drivers/iio/light/veml6075.c | 7 ++++++-
> 1 file changed, 6 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/iio/light/veml6075.c b/drivers/iio/light/veml6075.c
> index 05d4c0e9015d..5dd951f6e989 100644
> --- a/drivers/iio/light/veml6075.c
> +++ b/drivers/iio/light/veml6075.c
> @@ -201,7 +201,12 @@ static int veml6075_read_int_time_index(struct veml6075_data *data)
> if (ret < 0)
> return ret;
>
> - return FIELD_GET(VEML6075_CONF_IT, conf);
Please declare the variable at the beginning of the function (there are
some integers there already) and rename it to follow the driver
convention, it for integration time: it_index
> + int int_index = FIELD_GET(VEML6075_CONF_IT, conf);
> +
> + if (int_index >= ARRAY_SIZE(veml6075_it_ms))
> + return -EINVAL;
> +
> + return int_index;
> }
>
> static int veml6075_read_int_time_ms(struct veml6075_data *data, int *val)
With that applied:
Reviewed-by: Javier Carrasco <javier.carrasco@gmail.com>
next prev parent reply other threads:[~2025-02-20 20:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-20 17:34 [PATCH v3] iio: light: Add check for array bounds in veml6075_read_int_time_ms Karan Sanghavi
2025-02-20 20:00 ` Javier Carrasco [this message]
2025-02-20 20:02 ` Javier Carrasco
2025-02-22 16:43 ` Jonathan Cameron
2025-02-22 16:45 ` Jonathan Cameron
2025-03-08 16:50 ` Jonathan Cameron
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=D7XJGM6MAB6N.2FYSUN4OJELUA@gmail.com \
--to=javier.carrasco.cruz@gmail.com \
--cc=jic23@kernel.org \
--cc=karansanghvi98@gmail.com \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=skhan@linuxfoundation.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