Linux IIO development
 help / color / mirror / Atom feed
From: David Lechner <dlechner@baylibre.com>
To: Marcelo Schmitt <marcelo.schmitt1@gmail.com>
Cc: "Michael Hennerich" <Michael.Hennerich@analog.com>,
	"Jonathan Cameron" <jic23@kernel.org>,
	"Nuno Sá" <nuno.sa@analog.com>,
	"Andy Shevchenko" <andy@kernel.org>,
	"Jonathan Cameron" <Jonathan.Cameron@huawei.com>,
	linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
	"Dan Carpenter" <dan.carpenter@linaro.org>
Subject: Re: [PATCH] iio: adc: ad7124: fix possible OOB array access
Date: Wed, 22 Oct 2025 11:59:56 -0500	[thread overview]
Message-ID: <49c09806-0f58-4d1d-aa0c-4351fc3e7089@baylibre.com> (raw)
In-Reply-To: <aPkMLUhm_UAVzRSA@debian-BULLSEYE-live-builder-AMD64>

On 10/22/25 11:54 AM, Marcelo Schmitt wrote:
> Hi David,
> 
> One minor question inline.
> Nevertheless, the fix looks good to me.
> 
> Reviewed-by: Marcelo Schmitt <marcelo.schmitt@analog.com>
> 
> On 10/22, David Lechner wrote:
>> Reorder the channel bounds check before using it to index into the
>> channels array in ad7124_release_config_slot(). This prevents reading
>> past the end of the array.
>>
>> The value read from invalid memory was not used, so this was mostly
> What is considered using the value in this context? (see other comment below)
> 
>> harmless, but we still should not be reading out of bounds in the first
>> place.
>>
>> Reported-by: Dan Carpenter <dan.carpenter@linaro.org>
>> Closes: https://lore.kernel.org/linux-iio/aPi6V-hcaKReSNWK@stanley.mountain/
>> Fixes: 9065197e0d41 ("iio: adc: ad7124: change setup reg allocation strategy")
>> Signed-off-by: David Lechner <dlechner@baylibre.com>
>> ---
>>  drivers/iio/adc/ad7124.c | 13 +++++++++----
>>  1 file changed, 9 insertions(+), 4 deletions(-)
>>
>> diff --git a/drivers/iio/adc/ad7124.c b/drivers/iio/adc/ad7124.c
>> index 9d58ced7371d0af7004a81153888714e9795d4f4..ed828a82acb71342fb2eae27abfbbd86861cba53 100644
>> --- a/drivers/iio/adc/ad7124.c
>> +++ b/drivers/iio/adc/ad7124.c
>> @@ -586,13 +586,18 @@ static int ad7124_request_config_slot(struct ad7124_state *st, u8 channel)
>>  
>>  static void ad7124_release_config_slot(struct ad7124_state *st, u8 channel)
>>  {
>> -	unsigned int slot = st->channels[channel].cfg.cfg_slot;
>> +	unsigned int slot;
>>  
>>  	/*
>> -	 * All of these conditions can happen at probe when all channels are
>> -	 * disabled. Otherwise, they should not happen normally.
>> +	 * All of these early return conditions can happen at probe when all
>> +	 * channels are disabled. Otherwise, they should not happen normally.
>>  	 */
>> -	if (channel >= st->num_channels || slot == AD7124_CFG_SLOT_UNASSIGNED ||
>> +	if (channel >= st->num_channels)
>> +		return;
>> +
>> +	slot = st->channels[channel].cfg.cfg_slot;
>> +
>> +	if (slot == AD7124_CFG_SLOT_UNASSIGNED ||
>>  	    st->cfg_slot_use_count[slot] == 0)
> Wasn't the value potentially read from invalid memory used above?
> It's fixed now, so I guess there's no point in nitpicking on that.

This code was unreachable with an undefined slot even before
this change because of the check to channel >= st->num_channels
before it.

> 
>>  		return;
> 
> Best regards,
> Marcelo


  reply	other threads:[~2025-10-22 16:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-22 15:15 [PATCH] iio: adc: ad7124: fix possible OOB array access David Lechner
2025-10-22 16:54 ` Marcelo Schmitt
2025-10-22 16:59   ` David Lechner [this message]
2025-10-22 17:45     ` Marcelo Schmitt
2025-10-22 17:18 ` Dan Carpenter
2025-10-27 14:27 ` 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=49c09806-0f58-4d1d-aa0c-4351fc3e7089@baylibre.com \
    --to=dlechner@baylibre.com \
    --cc=Jonathan.Cameron@huawei.com \
    --cc=Michael.Hennerich@analog.com \
    --cc=andy@kernel.org \
    --cc=dan.carpenter@linaro.org \
    --cc=jic23@kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo.schmitt1@gmail.com \
    --cc=nuno.sa@analog.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