From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Weiming Shi <bestswngs@gmail.com>
Cc: Jean Delvare <jdelvare@suse.com>,
linux-i2c@vger.kernel.org, Xiang Mei <xmei5@asu.edu>
Subject: Re: [PATCH v2] i2c: stub: Reject I2C block transfers with invalid length
Date: Mon, 4 May 2026 13:25:25 +0200 [thread overview]
Message-ID: <afiCJQkF4-cRFrrf@ninjato> (raw)
In-Reply-To: <20260414172338.110830-2-bestswngs@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2138 bytes --]
On Wed, Apr 15, 2026 at 01:23:39AM +0800, Weiming Shi wrote:
> The I2C_SMBUS_I2C_BLOCK_DATA case in stub_xfer() uses data->block[0]
> as the transfer length. The existing check only clamps it to avoid
> overrunning the chip->words[256] register array, but does not validate
> it against I2C_SMBUS_BLOCK_MAX (32), which is the limit of the union
> i2c_smbus_data.block buffer (34 bytes total). The driver is a
> development/test tool (CONFIG_I2C_STUB=m, not built by default)
> that must be loaded with a chip_addr= parameter.
>
> A local user with access to /dev/i2c-* can issue an I2C_SMBUS ioctl
> with I2C_SMBUS_I2C_BLOCK_DATA and data->block[0] > 32, causing
> stub_xfer() to read or write past the end of the union
> i2c_smbus_data.block buffer:
>
> BUG: KASAN: stack-out-of-bounds in stub_xfer (drivers/i2c/i2c-stub.c:223)
> Read of size 1 at addr ffff88800abcfd92 by task exploit/81
> Call Trace:
> <TASK>
> stub_xfer (drivers/i2c/i2c-stub.c:223)
> __i2c_smbus_xfer (drivers/i2c/i2c-core-smbus.c:593)
> i2c_smbus_xfer (drivers/i2c/i2c-core-smbus.c:536)
> i2cdev_ioctl_smbus (drivers/i2c/i2c-dev.c:391)
> i2cdev_ioctl (drivers/i2c/i2c-dev.c:478)
> __x64_sys_ioctl (fs/ioctl.c:583)
> do_syscall_64 (arch/x86/entry/syscall_64.c:94)
> entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:130)
> </TASK>
>
> The bug exists because i2c-stub implements .smbus_xfer directly,
> bypassing the I2C_SMBUS_BLOCK_MAX validation in
> i2c_smbus_xfer_emulated(). The I2C_SMBUS_BLOCK_DATA case in the same
> function correctly validates against I2C_SMBUS_BLOCK_MAX, but the
> I2C_SMBUS_I2C_BLOCK_DATA case does not.
>
> Fix by rejecting transfers with data->block[0] == 0 or
> data->block[0] > I2C_SMBUS_BLOCK_MAX with -EINVAL, consistent with
> both the I2C_SMBUS_BLOCK_DATA case in the same function and the
> I2C_SMBUS_I2C_BLOCK_DATA validation in i2c_smbus_xfer_emulated().
>
> Fixes: 4710317891e4 ("i2c-stub: Implement I2C block support")
> Reported-by: Xiang Mei <xmei5@asu.edu>
> Signed-off-by: Weiming Shi <bestswngs@gmail.com>
Applied to for-current, thanks!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2026-05-04 11:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-14 17:23 [PATCH v2] i2c: stub: Reject I2C block transfers with invalid length Weiming Shi
2026-05-04 11:25 ` Wolfram Sang [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=afiCJQkF4-cRFrrf@ninjato \
--to=wsa+renesas@sang-engineering.com \
--cc=bestswngs@gmail.com \
--cc=jdelvare@suse.com \
--cc=linux-i2c@vger.kernel.org \
--cc=xmei5@asu.edu \
/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