mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Andy Shevchenko <andriy.shevchenko@intel.com>
Cc: Tristan Madani <tristmd@gmail.com>,
	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,
	tristan@talencesecurity.com
Subject: Re: [PATCH v7] iio: adc: pac1934: validate ACPI _DSM return type and bounds
Date: Tue, 3 Nov 2026 23:25:52 +0000	[thread overview]
Message-ID: <20261103232552.77b63ea7@jic23-hlaptop> (raw)
In-Reply-To: <aupL8Yb61IPDu_hH@ashevche-desk.local>

On Tue, 3 Nov 2026 23:02:41 +0200
Andy Shevchenko <andriy.shevchenko@intel.com> wrote:

> On Tue, Nov 03, 2026 at 06:50:26PM +0000, Tristan Madani 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.
> > 
> > Use acpi_evaluate_dsm_typed() with ACPI_TYPE_PACKAGE to validate the
> > return type at evaluation time.  Cap loop iterations to
> > PAC1934_MAX_NUM_CHANNELS, and verify package count >= 1 before
> > accessing elements[0].  
> 
> LGTM now,
> Reviewed-by: Andy Shevchenko <andriy.shevchenko@intel.com>
> 

Applied to the testing branch of iio.git.

Thanks,

Jonathan


      reply	other threads:[~2026-11-03 23:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-03 18:50 Tristan Madani
2026-11-03 21:02 ` Andy Shevchenko
2026-11-03 23:25   ` Jonathan Cameron [this message]

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=20261103232552.77b63ea7@jic23-hlaptop \
    --to=jic23@kernel.org \
    --cc=andriy.shevchenko@intel.com \
    --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=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®