From: Guenter Roeck <linux@roeck-us.net>
To: "Pradhan, Sanman" <sanman.pradhan@hpe.com>
Cc: "linux-hwmon@vger.kernel.org" <linux-hwmon@vger.kernel.org>,
"cosmo.chou@quantatw.com" <cosmo.chou@quantatw.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Sanman Pradhan <psanman@juniper.net>,
"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: [PATCH v4] hwmon: (pt5161l) Fix bugs in pt5161l_read_block_data()
Date: Fri, 10 Apr 2026 08:31:14 -0700 [thread overview]
Message-ID: <3dc5812c-1ced-4fad-82e8-ece32a30b9bb@roeck-us.net> (raw)
In-Reply-To: <20260410002549.424162-1-sanman.pradhan@hpe.com>
On Fri, Apr 10, 2026 at 12:25:55AM +0000, Pradhan, Sanman wrote:
> From: Sanman Pradhan <psanman@juniper.net>
>
> Fix two bugs in pt5161l_read_block_data():
>
> 1. Buffer overrun: The local buffer rbuf is declared as u8 rbuf[24],
> but i2c_smbus_read_block_data() can return up to
> I2C_SMBUS_BLOCK_MAX (32) bytes. The i2c-core copies the data into
> the caller's buffer before the return value can be checked, so
> the post-read length validation does not prevent a stack overrun
> if a device returns more than 24 bytes. Resize the buffer to
> I2C_SMBUS_BLOCK_MAX.
>
> 2. Unexpected positive return on length mismatch: When all three
> retries are exhausted because the device returns data with an
> unexpected length, i2c_smbus_read_block_data() returns a positive
> byte count. The function returns this directly, and callers treat
> any non-negative return as success, processing stale or incomplete
> buffer contents. Return -EIO when retries are exhausted with a
> positive return value, preserving the negative error code on I2C
> failure.
>
> Fixes: 1b2ca93cd0592 ("hwmon: Add driver for Astera Labs PT5161L retimer")
> Cc: stable@vger.kernel.org
> Signed-off-by: Sanman Pradhan <psanman@juniper.net>
Applied.
Thanks,
Guenter
prev parent reply other threads:[~2026-04-10 15:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-10 0:25 [PATCH v4] hwmon: (pt5161l) Fix bugs in pt5161l_read_block_data() Pradhan, Sanman
2026-04-10 15:31 ` Guenter Roeck [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=3dc5812c-1ced-4fad-82e8-ece32a30b9bb@roeck-us.net \
--to=linux@roeck-us.net \
--cc=cosmo.chou@quantatw.com \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=psanman@juniper.net \
--cc=sanman.pradhan@hpe.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