From: David Lechner <dlechner@baylibre.com>
To: Laxman Acharya Padhya <acharyalaxman8848@gmail.com>,
Jonathan Cameron <jic23@kernel.org>
Cc: "Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>,
"Yasin Lee" <yasin.lee.x@gmail.com>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH] iio: proximity: hx9023s: validate firmware size
Date: Fri, 10 Jul 2026 10:21:11 -0500 [thread overview]
Message-ID: <9845b343-8138-4858-93a2-df8e01c7d64f@baylibre.com> (raw)
In-Reply-To: <20260710142212.52225-1-acharyalaxman8848@gmail.com>
On 7/10/26 9:22 AM, Laxman Acharya Padhya wrote:
> hx9023s_send_cfg() copies the firmware into a counted flexible array and
> then reads fixed offsets from the copied data before walking register/value
> pairs starting at FW_DATA_OFFSET. A truncated firmware image can therefore
> make the driver read past the copied buffer during probe-time configuration
> loading.
>
> Reject firmware images that cannot contain the fixed header, reject images
> too large for the u16 fw_size field, and validate that the advertised
> register count fits in the remaining payload.
>
> Move release_firmware() to the callback so the firmware object is released
> on all hx9023s_send_cfg() error paths.
This could probably be considered a separate fix (and therefore separate
patch) since it looks like there is an existing code path (return -ENOMEM)
where it would not be released.
>
> Fixes: e9ed97be4fcc ("iio: proximity: hx9023s: Added firmware file parsing functionality")
> Cc: stable@vger.kernel.org
> Signed-off-by: Laxman Acharya Padhya <acharyalaxman8848@gmail.com>
> ---
> drivers/iio/proximity/hx9023s.c | 14 +++++++++++---
> 1 file changed, 11 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/iio/proximity/hx9023s.c b/drivers/iio/proximity/hx9023s.c
> index a6ff7cbe9e6..a2f9c077e58 100644
> --- a/drivers/iio/proximity/hx9023s.c
> +++ b/drivers/iio/proximity/hx9023s.c
> @@ -18,6 +18,7 @@
> #include <linux/i2c.h>
> #include <linux/interrupt.h>
> #include <linux/irqreturn.h>
> +#include <linux/limits.h>
> #include <linux/math64.h>
> #include <linux/module.h>
> #include <linux/mutex.h>
> @@ -25,6 +26,7 @@
> #include <linux/property.h>
> #include <linux/regmap.h>
> #include <linux/regulator/consumer.h>
> +#include <linux/slab.h>
> #include <linux/types.h>
> #include <linux/units.h>
>
> @@ -1031,8 +1033,12 @@ static int hx9023s_bin_load(struct hx9023s_data *data, struct hx9023s_bin *bin)
>
> static int hx9023s_send_cfg(const struct firmware *fw, struct hx9023s_data *data)
> {
> - struct hx9023s_bin *bin __free(kfree) =
> - kzalloc(fw->size + sizeof(*bin), GFP_KERNEL);
> + struct hx9023s_bin *bin __free(kfree) = NULL;
We don't initialize autocleanup variables to NULL. So leave this as-is
and just put the size check before it.
> +
> + if (fw->size < FW_DATA_OFFSET || fw->size > U16_MAX)
> + return -EINVAL;
> +
> + bin = kzalloc(sizeof(*bin) + fw->size, GFP_KERNEL);
> if (!bin)
> return -ENOMEM;
>
> @@ -1041,7 +1047,8 @@ static int hx9023s_send_cfg(const struct firmware *fw, struct hx9023s_data *data
> bin->fw_ver = bin->data[FW_VER_OFFSET];
> bin->reg_count = get_unaligned_le16(bin->data + FW_REG_CNT_OFFSET);
>
> - release_firmware(fw);
> + if (bin->reg_count > (bin->fw_size - FW_DATA_OFFSET) / 2)
> + return -EINVAL;
>
> return hx9023s_bin_load(data, bin);
> }
> @@ -1058,6 +1065,7 @@ static void hx9023s_cfg_update(const struct firmware *fw, void *context)
> }
>
> ret = hx9023s_send_cfg(fw, data);
> + release_firmware(fw);
> if (ret) {
> dev_warn(dev, "Firmware update failed: %d\n", ret);
> goto no_fw;
>
> base-commit: 0e35b9b6ec0ffcc5e23cbdec09f5c622ad532b53
next prev parent reply other threads:[~2026-07-10 15:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-10 14:22 Laxman Acharya Padhya
2026-07-10 14:54 ` Joshua Crofts
2026-07-10 15:22 ` David Lechner
2026-07-10 15:21 ` David Lechner [this message]
2026-07-10 15:28 ` [PATCH v2] " Laxman Acharya Padhya
2026-07-10 20:21 ` Jonathan Cameron
2026-07-11 9:03 ` 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=9845b343-8138-4858-93a2-df8e01c7d64f@baylibre.com \
--to=dlechner@baylibre.com \
--cc=acharyalaxman8848@gmail.com \
--cc=andy@kernel.org \
--cc=jic23@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.com \
--cc=stable@vger.kernel.org \
--cc=yasin.lee.x@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®