From: Jonathan Cameron <jic23@kernel.org>
To: Javier Carrasco <javier.carrasco.cruz@gmail.com>
Cc: "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 07/11] iio: light: bh1745: fix information leak in triggered buffer
Date: Sat, 30 Nov 2024 20:53:55 +0000 [thread overview]
Message-ID: <20241130205355.0c4238c7@jic23-huawei> (raw)
In-Reply-To: <20241125-iio_memset_scan_holes-v1-7-0cb6e98d895c@gmail.com>
On Mon, 25 Nov 2024 22:16:15 +0100
Javier Carrasco <javier.carrasco.cruz@gmail.com> wrote:
> The 'scan' local struct is used to push data to user space from a
> triggered buffer, but it does not set values for inactive channels, as
> it only uses iio_for_each_active_channel() to assign new values.
>
> Initialize the struct to zero before using it to avoid pushing
> uninitialized information to userspace.
>
> Cc: stable@vger.kernel.org
> Fixes: eab35358aae7 ("iio: light: ROHM BH1745 colour sensor")
> Signed-off-by: Javier Carrasco <javier.carrasco.cruz@gmail.com>
Applied.
> ---
> drivers/iio/light/bh1745.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/drivers/iio/light/bh1745.c b/drivers/iio/light/bh1745.c
> index 23e9f16090cc..2ffc839c7501 100644
> --- a/drivers/iio/light/bh1745.c
> +++ b/drivers/iio/light/bh1745.c
> @@ -746,6 +746,8 @@ static irqreturn_t bh1745_trigger_handler(int interrupt, void *p)
> int i;
> int j = 0;
>
> + memset(&scan, 0, sizeof(scan));
> +
> iio_for_each_active_channel(indio_dev, i) {
> ret = regmap_bulk_read(data->regmap, BH1745_RED_LSB + 2 * i,
> &value, 2);
>
next prev parent reply other threads:[~2024-11-30 20:54 UTC|newest]
Thread overview: 33+ 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
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 [this message]
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
2024-11-25 21:16 ` [PATCH 11/11] iio: core: fix doc reference to iio_push_to_buffers_with_ts_unaligned Javier Carrasco
2024-11-30 20:42 ` 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=20241130205355.0c4238c7@jic23-huawei \
--to=jic23@kernel.org \
--cc=Jonathan.Cameron@huawei.com \
--cc=apokusinski01@gmail.com \
--cc=francesco.dolcini@toradex.com \
--cc=francesco@dolcini.it \
--cc=gregor.boirie@parrot.com \
--cc=javier.carrasco.cruz@gmail.com \
--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