From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Weigang He <geoffreyhe2@gmail.com>
Cc: "Jonathan Cameron" <jic23@kernel.org>,
"Sai Krishna Potthuri" <sai.krishna.potthuri@amd.com>,
"Conall O'Griofa" <conall.ogriofa@amd.com>,
"David Lechner" <dlechner@baylibre.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>,
"Michal Simek" <michal.simek@amd.com>,
linux-iio@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH] iio: adc: xilinx-ams: fix out-of-bounds accesses when parsing channels
Date: Mon, 28 Sep 2026 11:22:59 +0300 [thread overview]
Message-ID: <aroj4-Wag_kxuBxH@ashevche-desk.local> (raw)
In-Reply-To: <20260926055456.3289189-1-geoffreyhe2@gmail.com>
On Sat, Sep 26, 2026 at 03:54:56PM +1000, Weigang He wrote:
> ams_parse_firmware() allocates room for ARRAY_SIZE(ams_ps_channels) +
> ARRAY_SIZE(ams_pl_channels) + ARRAY_SIZE(ams_ctrl_channels) = 51
> channel specs and lets ams_init_module() fill them for the AMS node and
> each of its children, without telling it how much room is left.
>
> For the PL-SYSMON node, ams_get_ext_chan() appends one channel per
> "channel@N" child after the 10 fixed PL channels. The binding allows
> reg values 20..50, so a PL node can have up to 31 such children, i.e.
> up to 41 PL channels, while only 31 are budgeted for it. Together with
> the 13 PS and 7 AMS control channels, this writes past the end of the
> buffer. Since the modules are filled in device tree order, the fixed
> channel blocks copied after the PL node can overflow as well.
>
> ams_get_ext_chan() also only checks the upper bound of reg. ext_chan is
> unsigned, so a reg below 20 makes it wrap and ams_pl_channels[] is read
> far out of bounds.
>
> Pass the remaining capacity down to ams_init_module() and
> ams_get_ext_chan() and fail with -EINVAL when a module does not fit,
> instead of writing past the buffer. Also reject reg values below 20, as
> the binding requires.
>
> Found by static analysis tool CodeQL.
...
> fwnode_for_each_child_node(chan_node, child) {
It seems better to switch to _scoped() variant at some point.
> ret = fwnode_property_read_u32(child, "reg", ®);
> - if (ret || reg > AMS_PL_MAX_EXT_CHANNEL + 30)
> + if (ret || reg < 30 - AMS_PL_MAX_FIXED_CHANNEL ||
> + reg > AMS_PL_MAX_EXT_CHANNEL + 30)
> continue;
>
> + if (num_channels >= max_channels) {
> + fwnode_handle_put(child);
> + return -EINVAL;
-ECHRNG
> + }
...
> if (fwnode_device_is_compatible(fwnode, "xlnx,zynqmp-ams-ps")) {
> + if (max_channels < ARRAY_SIZE(ams_ps_channels))
> + return -EINVAL;
ENOSPC?
...
> } else if (fwnode_device_is_compatible(fwnode, "xlnx,zynqmp-ams-pl")) {
> + if (max_channels < AMS_PL_MAX_FIXED_CHANNEL)
> + return -EINVAL;
Ditto.
...
> } else if (fwnode_device_is_compatible(fwnode, "xlnx,zynqmp-ams")) {
> + if (max_channels < ARRAY_SIZE(ams_ctrl_channels))
> + return -EINVAL;
Ditto.
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2026-09-28 8:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-26 5:54 [PATCH] iio: adc: xilinx-ams: fix out-of-bounds accesses when parsing channels Weigang He
2026-09-28 8:22 ` Andy Shevchenko [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=aroj4-Wag_kxuBxH@ashevche-desk.local \
--to=andriy.shevchenko@intel.com \
--cc=andy@kernel.org \
--cc=conall.ogriofa@amd.com \
--cc=dlechner@baylibre.com \
--cc=geoffreyhe2@gmail.com \
--cc=jic23@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.simek@amd.com \
--cc=nuno.sa@analog.com \
--cc=sai.krishna.potthuri@amd.com \
--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