From: Jonathan Cameron <jic23@kernel.org>
To: Tristan Madani <tristmd@gmail.com>
Cc: Marius Cristea <marius.cristea@microchip.com>,
David Lechner <dlechner@baylibre.com>,
Nuno Sa <nuno.sa@analog.com>, Andy Shevchenko <andy@kernel.org>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org, tristan@talencesecurity.com
Subject: Re: [PATCH] iio: adc: pac1934: validate ACPI _DSM return type and bounds
Date: Tue, 27 Oct 2026 01:09:40 +0000 [thread overview]
Message-ID: <20261027010940.50bd884a@jic23-hlaptop> (raw)
In-Reply-To: <20261026230910.2569782-1-tristan@talencesecurity.com>
On Mon, 26 Oct 2026 23:09:10 +0000
Tristan Madani <tristmd@gmail.com> wrote:
> pac1934_acpi_parse_channel_config() calls acpi_evaluate_dsm() four
> times to read channel configuration but does not validate the returned
> object type or array bounds:
>
> 1. No check that the returned object is ACPI_TYPE_PACKAGE. If
> firmware returns a different type, accessing rez->package.count
> and rez->package.elements on a non-package object produces
> unpredictable values.
>
> 2. The loop bounds use rez->package.count directly without capping
> to PAC1934_MAX_NUM_CHANNELS (4). A package with more elements
> than expected causes writes past the fixed-size labels[],
> shunts[], and active_channels[] arrays.
>
> 3. The bipolar and sample rate DSM calls access elements[0] without
> verifying package.count >= 1.
>
> Add ACPI_TYPE_PACKAGE validation after each acpi_evaluate_dsm() call,
> cap loop iterations to PAC1934_MAX_NUM_CHANNELS, and verify package
> count >= 1 before accessing elements[0].
>
> Fixes: 0fb528c8255b ("iio: adc: adding support for PAC193x")
I should have mentioned this for earlier patches. This is
to my eyes not a fix, it is hardening against buggy firmware.
Now I'm fine with doing such hardening but we don't want to
suggest it is something folk should definitely backport.
> Cc: stable@vger.kernel.org
> Signed-off-by: Tristan Madani <tristan@talencesecurity.com>
> ---
> drivers/iio/adc/pac1934.c | 23 +++++++++++++++++++++--
> 1 file changed, 21 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/iio/adc/pac1934.c b/drivers/iio/adc/pac1934.c
> index de59dc27c4405..43c4705c27be7 100644
> --- a/drivers/iio/adc/pac1934.c
> +++ b/drivers/iio/adc/pac1934.c
> @@ -1101,8 +1101,13 @@ static int pac1934_acpi_parse_channel_config(struct i2c_client *client,
> rez = acpi_evaluate_dsm(handle, &guid, 0, PAC1934_ACPI_GET_NAMES_AND_MOHMS_VALS, NULL);
> if (!rez)
> return -EINVAL;
> + if (rez->type != ACPI_TYPE_PACKAGE) {
> + ACPI_FREE(rez);
> + return -EINVAL;
> + }
>
> - for (i = 0; i < rez->package.count; i += 2) {
> + for (i = 0; i + 1 < rez->package.count &&
> + i / 2 < PAC1934_MAX_NUM_CHANNELS; i += 2) {
> idx = i / 2;
> info->labels[idx] =
> devm_kmemdup(dev, rez->package.elements[i].string.pointer,
> @@ -1130,7 +1135,13 @@ static int pac1934_acpi_parse_channel_config(struct i2c_client *client,
> return 0;
> }
>
> - for (i = 0; i < rez->package.count; i++) {
> + if (rez->type != ACPI_TYPE_PACKAGE) {
> + ACPI_FREE(rez);
> + return -EINVAL;
> + }
> +
> + for (i = 0; i < rez->package.count &&
> + i < PAC1934_MAX_NUM_CHANNELS; i++) {
> idx = i;
> info->shunts[idx] = rez->package.elements[i].integer.value;
> info->active_channels[idx] = (info->shunts[idx] != 0);
> @@ -1141,6 +1152,10 @@ static int pac1934_acpi_parse_channel_config(struct i2c_client *client,
> rez = acpi_evaluate_dsm(handle, &guid, 1, PAC1934_ACPI_GET_BIPOLAR_SETTINGS, NULL);
> if (!rez)
> return -EINVAL;
> + if (rez->type != ACPI_TYPE_PACKAGE || rez->package.count < 1) {
> + ACPI_FREE(rez);
> + return -EINVAL;
> + }
>
> bi_dir_mask = rez->package.elements[0].integer.value;
> info->bi_dir[0] = ((bi_dir_mask & (1 << 3)) | (bi_dir_mask & (1 << 7))) != 0;
> @@ -1153,6 +1168,10 @@ static int pac1934_acpi_parse_channel_config(struct i2c_client *client,
> rez = acpi_evaluate_dsm(handle, &guid, 1, PAC1934_ACPI_GET_SAMP, NULL);
> if (!rez)
> return -EINVAL;
> + if (rez->type != ACPI_TYPE_PACKAGE || rez->package.count < 1) {
> + ACPI_FREE(rez);
> + return -EINVAL;
> + }
>
> info->sample_rate_value = rez->package.elements[0].integer.value;
>
next prev parent reply other threads:[~2026-10-27 1:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-26 23:09 Tristan Madani
2026-10-27 1:09 ` Jonathan Cameron [this message]
2026-10-27 7:40 ` Andy Shevchenko
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=20261027010940.50bd884a@jic23-hlaptop \
--to=jic23@kernel.org \
--cc=andy@kernel.org \
--cc=dlechner@baylibre.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marius.cristea@microchip.com \
--cc=nuno.sa@analog.com \
--cc=stable@vger.kernel.org \
--cc=tristan@talencesecurity.com \
--cc=tristmd@gmail.com \
/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
all inboxes | Powered by JetHome®