summaryrefslogtreecommitdiffstats
path: root/drivers/dax
diff options
context:
space:
mode:
authorJonathan Cameron <Jonathan.Cameron@huawei.com>2020-07-22 16:51:03 +0100
committerJonathan Cameron <Jonathan.Cameron@huawei.com>2020-08-31 10:47:52 +0100
commitdb8f06d97ec284dc018e2e4890d2e5035fde8630 (patch)
treea754b712ba1e496d4796eb673cd4e4527083260c /drivers/dax
parentf8cd222feb82ecd82dcf610fcc15186f55f9c2b5 (diff)
downloadlinux-stable-db8f06d97ec284dc018e2e4890d2e5035fde8630.tar.gz
linux-stable-db8f06d97ec284dc018e2e4890d2e5035fde8630.tar.bz2
linux-stable-db8f06d97ec284dc018e2e4890d2e5035fde8630.zip
iio:adc:max1118 Fix alignment of timestamp and data leak issues
One of a class of bugs pointed out by Lars in a recent review. iio_push_to_buffers_with_timestamp assumes the buffer used is aligned to the size of the timestamp (8 bytes). This is not guaranteed in this driver which uses an array of smaller elements on the stack. As Lars also noted this anti pattern can involve a leak of data to userspace and that indeed can happen here. We close both issues by moving to a suitable structure in the iio_priv() data. This data is allocated with kzalloc so no data can leak apart from previous readings. The explicit alignment of ts is necessary to ensure correct padding on architectures where s64 is only 4 bytes aligned such as x86_32. Fixes: a9e9c7153e96 ("iio: adc: add max1117/max1118/max1119 ADC driver") Reported-by: Lars-Peter Clausen <lars@metafoo.de> Cc: Akinobu Mita <akinobu.mita@gmail.com> Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com> Reviewed-by: Andy Shevchenko <andy.shevchenko@gmail.com> Cc: <Stable@vger.kernel.org>
Diffstat (limited to 'drivers/dax')
0 files changed, 0 insertions, 0 deletions