From: David Lechner <dlechner@baylibre.com>
To: Dan Carpenter <dan.carpenter@linaro.org>
Cc: linux-iio@vger.kernel.org
Subject: Re: [bug report] iio: pressure: bmp280: drop sensor_data array
Date: Tue, 6 May 2025 09:25:00 -0500 [thread overview]
Message-ID: <487c81af-6604-4881-ae78-2d41ce23396f@baylibre.com> (raw)
In-Reply-To: <aBoBR5D1UMjsSUfZ@stanley.mountain>
On 5/6/25 7:32 AM, Dan Carpenter wrote:
> Hello David Lechner,
>
> Commit 4e6c3c4801a6 ("iio: pressure: bmp280: drop sensor_data array")
> from Apr 22, 2025 (linux-next), leads to the following Smatch static
> checker warning:
>
> drivers/iio/pressure/bmp280-core.c:1280 bme280_trigger_handler()
> warn: check that 'buffer' doesn't leak information (struct has a hole after 'comp_humidity')
>
> drivers/iio/pressure/bmp280-core.c
> 1225 static irqreturn_t bme280_trigger_handler(int irq, void *p)
> 1226 {
> 1227 struct iio_poll_func *pf = p;
> 1228 struct iio_dev *indio_dev = pf->indio_dev;
> 1229 struct bmp280_data *data = iio_priv(indio_dev);
> 1230 u32 adc_temp, adc_press, adc_humidity;
> 1231 s32 t_fine;
> 1232 struct {
> 1233 u32 comp_press;
> 1234 s32 comp_temp;
> 1235 u32 comp_humidity;
> 1236 aligned_s64 timestamp;
>
> There is a 4 byte hole between comp_humidity and timestamp.
Yes, this was the intention of this patch.
>
> 1237 } buffer;
> 1238 int ret;
> 1239
...
> 1279
> --> 1280 iio_push_to_buffers_with_ts(indio_dev, &buffer, sizeof(buffer),
> ^^^^^^^^^^^^^^^^^^^^^^^
> So I believe it leads to an information leaks here.
Aha, so we should e.g. do memset() to fill the hole first.
>
> 1281 iio_get_time_ns(indio_dev));
> 1282
> 1283 out:
> 1284 iio_trigger_notify_done(indio_dev->trig);
> 1285
> 1286 return IRQ_HANDLED;
> 1287 }
>
> regards,
> dan carpenter
next prev parent reply other threads:[~2025-05-06 14:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-06 12:32 [bug report] iio: pressure: bmp280: drop sensor_data array Dan Carpenter
2025-05-06 14:25 ` David Lechner [this message]
2025-05-06 18:35 ` Dan Carpenter
2025-05-07 6:35 ` Jonathan Cameron
2025-05-07 7:41 ` Dan Carpenter
2025-05-07 13:33 ` David Lechner
2025-05-09 5:49 ` Dan Carpenter
2025-05-09 10:01 ` Dan Carpenter
2025-05-09 16:58 ` Kees Cook
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=487c81af-6604-4881-ae78-2d41ce23396f@baylibre.com \
--to=dlechner@baylibre.com \
--cc=dan.carpenter@linaro.org \
--cc=linux-iio@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