From: Francesco Dolcini <francesco@dolcini.it>
To: Javier Carrasco <javier.carrasco.cruz@gmail.com>
Cc: "Jonathan Cameron" <jic23@kernel.org>,
"Lars-Peter Clausen" <lars@metafoo.de>,
"Antoni Pokusinski" <apokusinski01@gmail.com>,
"Francesco Dolcini" <francesco@dolcini.it>,
"João Paulo Gonçalves" <jpaulo.silvagoncalves@gmail.com>,
"Gregor Boirie" <gregor.boirie@parrot.com>,
"Jonathan Cameron" <Jonathan.Cameron@huawei.com>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
"João Paulo Gonçalves" <joao.goncalves@toradex.com>,
"Francesco Dolcini" <francesco.dolcini@toradex.com>,
stable@vger.kernel.org
Subject: Re: [PATCH 02/11] iio: adc: ti-ads1119: fix information leak in triggered buffer
Date: Tue, 26 Nov 2024 09:59:58 +0100 [thread overview]
Message-ID: <20241126085958.GA13577@francesco-nb> (raw)
In-Reply-To: <20241125-iio_memset_scan_holes-v1-2-0cb6e98d895c@gmail.com>
On Mon, Nov 25, 2024 at 10:16:10PM +0100, Javier Carrasco wrote:
> The 'scan' local struct is used to push data to user space from a
> triggered buffer, but it has a hole between the sample (unsigned int)
> and the timestamp. This hole is never initialized.
>
> Initialize the struct to zero before using it to avoid pushing
> uninitialized information to userspace.
>
> Cc: stable@vger.kernel.org
> Fixes: a9306887eba4 ("iio: adc: ti-ads1119: Add driver")
> Signed-off-by: Javier Carrasco <javier.carrasco.cruz@gmail.com>
> ---
> drivers/iio/adc/ti-ads1119.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/drivers/iio/adc/ti-ads1119.c b/drivers/iio/adc/ti-ads1119.c
> index e9d9d4d46d38..2615a275acb3 100644
> --- a/drivers/iio/adc/ti-ads1119.c
> +++ b/drivers/iio/adc/ti-ads1119.c
> @@ -506,6 +506,8 @@ static irqreturn_t ads1119_trigger_handler(int irq, void *private)
> unsigned int index;
> int ret;
>
> + memset(&scan, 0, sizeof(scan));
Did you consider adding a reserved field after sample and just
initializing that one to zero?
It seems a trivial optimization not adding much value, but I thought about
it, so I'd like to be sure you considered it.
In any case, the change is fine.
Reviewed-by: Francesco Dolcini <francesco.dolcini@toradex.com>
Thanks,
Francesco
next prev parent reply other threads:[~2024-11-26 9:00 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-25 21:16 [PATCH 00/11] iio: fix information leaks in triggered buffers Javier Carrasco
2024-11-25 21:16 ` [PATCH 01/11] iio: temperature: tmp006: fix information leak in triggered buffer Javier Carrasco
2024-12-02 19:28 ` Javier Carrasco
2024-12-08 18:36 ` Jonathan Cameron
2024-11-25 21:16 ` [PATCH 02/11] iio: adc: ti-ads1119: " Javier Carrasco
2024-11-26 8:59 ` Francesco Dolcini [this message]
2024-11-26 9:46 ` Javier Carrasco
2024-11-26 18:52 ` Jonathan Cameron
2024-11-26 22:00 ` Javier Carrasco
2024-11-27 0:30 ` Javier Carrasco
2024-11-30 20:43 ` Jonathan Cameron
2024-11-30 21:00 ` Jonathan Cameron
2024-11-25 21:16 ` [PATCH 03/11] iio: pressure: zpa2326: " Javier Carrasco
2024-11-30 20:59 ` Jonathan Cameron
2024-11-25 21:16 ` [PATCH 04/11] iio: adc: rockchip_saradc: " Javier Carrasco
2024-11-30 20:59 ` Jonathan Cameron
2024-11-25 21:16 ` [PATCH 05/11] iio: imu: kmx61: " Javier Carrasco
2024-11-30 20:56 ` Jonathan Cameron
2024-11-25 21:16 ` [PATCH 06/11] iio: light: vcnl4035: " Javier Carrasco
2024-11-30 20:55 ` Jonathan Cameron
2024-11-25 21:16 ` [PATCH 07/11] iio: light: bh1745: " Javier Carrasco
2024-11-30 20:53 ` Jonathan Cameron
2024-11-25 21:16 ` [PATCH 08/11] iio: adc: ti-ads8688: " Javier Carrasco
2024-11-30 20:52 ` Jonathan Cameron
2024-11-25 21:16 ` [PATCH 09/11] iio: dummy: iio_simply_dummy_buffer: " Javier Carrasco
2024-11-30 20:50 ` Jonathan Cameron
2024-11-25 21:16 ` [PATCH 10/11] iio: light: as73211: " Javier Carrasco
2024-11-30 20:49 ` Jonathan Cameron
2024-12-02 15:38 ` Javier Carrasco
2024-12-02 18:00 ` Christian Eggers
2024-12-02 19:14 ` Javier Carrasco
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=20241126085958.GA13577@francesco-nb \
--to=francesco@dolcini.it \
--cc=Jonathan.Cameron@huawei.com \
--cc=apokusinski01@gmail.com \
--cc=francesco.dolcini@toradex.com \
--cc=gregor.boirie@parrot.com \
--cc=javier.carrasco.cruz@gmail.com \
--cc=jic23@kernel.org \
--cc=joao.goncalves@toradex.com \
--cc=jpaulo.silvagoncalves@gmail.com \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.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