linux-iio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* [PATCH] iio: adis_buffer: Fix out-of-bounds memory access
@ 2015-11-27 13:55 Lars-Peter Clausen
  2015-11-29 14:22 ` Jonathan Cameron
  0 siblings, 1 reply; 2+ messages in thread
From: Lars-Peter Clausen @ 2015-11-27 13:55 UTC (permalink / raw)
  To: Jonathan Cameron
  Cc: Hartmut Knaack, Peter Meerwald-Stadler, linux-iio,
	Lars-Peter Clausen

The SPI tx and rx buffers are both supposed to be scan_bytes amount of
bytes large and a common allocation is used to allocate both buffers. This
puts the beginning of the tx buffer scan_bytes bytes after the rx buffer.
The initialization of the tx buffer pointer is done adding scan_bytes to
the beginning of the rx buffer, but since the rx buffer is of type __be16
this will actually add two times as much and the tx buffer ends up pointing
after the allocated buffer.

Fix this by using scan_count, which is scan_bytes / 2, instead of
scan_bytes when initializing the tx buffer pointer.

Fixes: aacff892cbd5 ("staging:iio:adis: Preallocate transfer message")
Signed-off-by: Lars-Peter Clausen <lars@metafoo.de>
---
Apologies if you got this twice, forgot the mailinglist on the first try.
---
 drivers/iio/imu/adis_buffer.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/iio/imu/adis_buffer.c b/drivers/iio/imu/adis_buffer.c
index cb32b59..36607d5 100644
--- a/drivers/iio/imu/adis_buffer.c
+++ b/drivers/iio/imu/adis_buffer.c
@@ -43,7 +43,7 @@ int adis_update_scan_mode(struct iio_dev *indio_dev,
 		return -ENOMEM;
 
 	rx = adis->buffer;
-	tx = rx + indio_dev->scan_bytes;
+	tx = rx + scan_count;
 
 	spi_message_init(&adis->msg);
 
-- 
2.1.4


^ permalink raw reply related	[flat|nested] 2+ messages in thread

* Re: [PATCH] iio: adis_buffer: Fix out-of-bounds memory access
  2015-11-27 13:55 [PATCH] iio: adis_buffer: Fix out-of-bounds memory access Lars-Peter Clausen
@ 2015-11-29 14:22 ` Jonathan Cameron
  0 siblings, 0 replies; 2+ messages in thread
From: Jonathan Cameron @ 2015-11-29 14:22 UTC (permalink / raw)
  To: Lars-Peter Clausen; +Cc: Hartmut Knaack, Peter Meerwald-Stadler, linux-iio

On 27/11/15 13:55, Lars-Peter Clausen wrote:
> The SPI tx and rx buffers are both supposed to be scan_bytes amount of
> bytes large and a common allocation is used to allocate both buffers. This
> puts the beginning of the tx buffer scan_bytes bytes after the rx buffer.
> The initialization of the tx buffer pointer is done adding scan_bytes to
> the beginning of the rx buffer, but since the rx buffer is of type __be16
> this will actually add two times as much and the tx buffer ends up pointing
> after the allocated buffer.
> 
> Fix this by using scan_count, which is scan_bytes / 2, instead of
> scan_bytes when initializing the tx buffer pointer.
> 
> Fixes: aacff892cbd5 ("staging:iio:adis: Preallocate transfer message")
> Signed-off-by: Lars-Peter Clausen <lars@metafoo.de>
Applied to my local fixes branch - will push out once Greg has caught
up with last pull request - don't want to muddy the waters!

Jonathan
> ---
> Apologies if you got this twice, forgot the mailinglist on the first try.
> ---
>  drivers/iio/imu/adis_buffer.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/iio/imu/adis_buffer.c b/drivers/iio/imu/adis_buffer.c
> index cb32b59..36607d5 100644
> --- a/drivers/iio/imu/adis_buffer.c
> +++ b/drivers/iio/imu/adis_buffer.c
> @@ -43,7 +43,7 @@ int adis_update_scan_mode(struct iio_dev *indio_dev,
>  		return -ENOMEM;
>  
>  	rx = adis->buffer;
> -	tx = rx + indio_dev->scan_bytes;
> +	tx = rx + scan_count;
>  
>  	spi_message_init(&adis->msg);
>  
> 


^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2015-11-29 14:22 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2015-11-27 13:55 [PATCH] iio: adis_buffer: Fix out-of-bounds memory access Lars-Peter Clausen
2015-11-29 14:22 ` Jonathan Cameron

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).