Linux IIO development
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Wei Yongjun <weiyongjun@huaweicloud.com>
Cc: "Lars-Peter Clausen" <lars@metafoo.de>,
	"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
	"Benjamin Mugnier" <benjamin.mugnier@foss.st.com>,
	"Andy Shevchenko" <andriy.shevchenko@linux.intel.com>,
	"Krzysztof Hałasa" <khalasa@piap.pl>,
	"Andrew F. Davis" <afd@ti.com>,
	"Wei Yongjun" <weiyongjun1@huawei.com>,
	linux-iio@vger.kernel.org
Subject: Re: [PATCH v3] iio: health: afe4404: Fix oob read in afe4404_[read|write]_raw
Date: Sat, 12 Nov 2022 16:31:04 +0000	[thread overview]
Message-ID: <20221112163104.3c34631d@jic23-huawei> (raw)
In-Reply-To: <20221107152010.95937-1-weiyongjun@huaweicloud.com>

On Mon,  7 Nov 2022 15:20:10 +0000
Wei Yongjun <weiyongjun@huaweicloud.com> wrote:

> From: Wei Yongjun <weiyongjun1@huawei.com>
> 
> KASAN report out-of-bounds read as follows:
> 
> BUG: KASAN: global-out-of-bounds in afe4404_read_raw+0x2ce/0x380
> Read of size 4 at addr ffffffffc00e4658 by task cat/278
> 
> Call Trace:
>  afe4404_read_raw
>  iio_read_channel_info
>  dev_attr_show
> 
> The buggy address belongs to the variable:
>  afe4404_channel_leds+0x18/0xffffffffffffe9c0
> 
> This issue can be reproduce by singe command:
> 
>  $ cat /sys/bus/i2c/devices/0-0058/iio\:device0/in_intensity6_raw
> 
> The array size of afe4404_channel_leds and afe4404_channel_offdacs
> are less than channels, so access with chan->address cause OOB read
> in afe4404_[read|write]_raw. Fix it by moving access before use them.
> 
> Fixes: b36e8257641a ("iio: health/afe440x: Use regmap fields")
> Signed-off-by: Wei Yongjun <weiyongjun1@huawei.com>
> Acked-by: Andrew Davis <afd@ti.com>

Applied to the fixes-togreg branch of iio.git.

Thanks,

Jonathan
> ---
> v2 -> v3: re-format backtraces
> v1 -> v2: also moved 'reg' to right before we use it
>           added Acked-by
> 
>  drivers/iio/health/afe4404.c | 12 +++++++-----
>  1 file changed, 7 insertions(+), 5 deletions(-)
> 
> diff --git a/drivers/iio/health/afe4404.c b/drivers/iio/health/afe4404.c
> index 8fca787b2524..836da31b7e30 100644
> --- a/drivers/iio/health/afe4404.c
> +++ b/drivers/iio/health/afe4404.c
> @@ -250,20 +250,20 @@ static int afe4404_read_raw(struct iio_dev *indio_dev,
>  			    int *val, int *val2, long mask)
>  {
>  	struct afe4404_data *afe = iio_priv(indio_dev);
> -	unsigned int value_reg = afe4404_channel_values[chan->address];
> -	unsigned int led_field = afe4404_channel_leds[chan->address];
> -	unsigned int offdac_field = afe4404_channel_offdacs[chan->address];
> +	unsigned int value_reg, led_field, offdac_field;
>  	int ret;
>  
>  	switch (chan->type) {
>  	case IIO_INTENSITY:
>  		switch (mask) {
>  		case IIO_CHAN_INFO_RAW:
> +			value_reg = afe4404_channel_values[chan->address];
>  			ret = regmap_read(afe->regmap, value_reg, val);
>  			if (ret)
>  				return ret;
>  			return IIO_VAL_INT;
>  		case IIO_CHAN_INFO_OFFSET:
> +			offdac_field = afe4404_channel_offdacs[chan->address];
>  			ret = regmap_field_read(afe->fields[offdac_field], val);
>  			if (ret)
>  				return ret;
> @@ -273,6 +273,7 @@ static int afe4404_read_raw(struct iio_dev *indio_dev,
>  	case IIO_CURRENT:
>  		switch (mask) {
>  		case IIO_CHAN_INFO_RAW:
> +			led_field = afe4404_channel_leds[chan->address];
>  			ret = regmap_field_read(afe->fields[led_field], val);
>  			if (ret)
>  				return ret;
> @@ -295,19 +296,20 @@ static int afe4404_write_raw(struct iio_dev *indio_dev,
>  			     int val, int val2, long mask)
>  {
>  	struct afe4404_data *afe = iio_priv(indio_dev);
> -	unsigned int led_field = afe4404_channel_leds[chan->address];
> -	unsigned int offdac_field = afe4404_channel_offdacs[chan->address];
> +	unsigned int led_field, offdac_field;
>  
>  	switch (chan->type) {
>  	case IIO_INTENSITY:
>  		switch (mask) {
>  		case IIO_CHAN_INFO_OFFSET:
> +			offdac_field = afe4404_channel_offdacs[chan->address];
>  			return regmap_field_write(afe->fields[offdac_field], val);
>  		}
>  		break;
>  	case IIO_CURRENT:
>  		switch (mask) {
>  		case IIO_CHAN_INFO_RAW:
> +			led_field = afe4404_channel_leds[chan->address];
>  			return regmap_field_write(afe->fields[led_field], val);
>  		}
>  		break;


      reply	other threads:[~2022-11-12 16:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-07 15:20 [PATCH v3] iio: health: afe4404: Fix oob read in afe4404_[read|write]_raw Wei Yongjun
2022-11-12 16:31 ` Jonathan Cameron [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=20221112163104.3c34631d@jic23-huawei \
    --to=jic23@kernel.org \
    --cc=afd@ti.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=benjamin.mugnier@foss.st.com \
    --cc=khalasa@piap.pl \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=u.kleine-koenig@pengutronix.de \
    --cc=weiyongjun1@huawei.com \
    --cc=weiyongjun@huaweicloud.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