High 7.8Published Jul 20, 2026

CVE-2026-64191i2c: stub: Reject I2C block transfers with invalid length

Updated under an hour ago (2026-10-19 08:50 UTC)

Does this affect you?

It affects Linux and 1 other product. Add what you run to find out whether that includes you.

No exploitation reported and no EPSS estimate yet.

Do this next

Start free and add your stack

Free account, 1 product

Every CVE for Linux

Exploited in the last 30 days

In the Linux kernel, the following vulnerability has been resolved: i2c: stub: Reject I2C block transfers with invalid length 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().

CVSS: 7.8 HIGH (v3.1, CNA)CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Weakness (CWE): Not given
Known exploited: Not in CISA's KEV catalog
EPSS (exploitation in the next 30 days): Not loaded for this CVE
Assigned by: Linux
NVD analysis: Analyzed
Record last updated: Oct 16, 2026
First seen by InfoSec Signals: Oct 9, 2026

Affected products

Affected products

Linux Linux linux:linux (from the name)	4710317891e4824ce1510a6b5066abbd3e917750 builds before 7e9072dbd5f2f17934751873450d2c22080ead80; 4710317891e4824ce1510a6b5066abbd3e917750 builds before 21e87f336ac6303fed54a69b1d0d79a23b25c8d0; 4710317891e4824ce1510a6b5066abbd3e917750 builds before 3fd225f3e4cd67ec8ddab1afed9da03c7c43537c; 4710317891e4824ce1510a6b5066abbd3e917750 builds before 1c4ffe6b4f04365485ed58d64c9bb86b46fc9037; 4710317891e4824ce1510a6b5066abbd3e917750 builds before 4bd8635f28c135a08aac6badcd7d9b5cdb34335f; 4710317891e4824ce1510a6b5066abbd3e917750 builds before 5f4d2bd028ebb6e4c09a9d64842546022321d4a7; 4710317891e4824ce1510a6b5066abbd3e917750 builds before 0526931b16e5a118d367b7bfce7d797e63f7ac69; 4710317891e4824ce1510a6b5066abbd3e917750 builds before 6036b5067a8199ba7a2dc7b377d4b9dd276d5f9e	CNA record
linux linux_kernel linux:linux_kernel	from 2.6.33 before 5.10.260; from 5.11 before 5.15.211; from 5.16 before 6.1.177; from 6.2 before 6.6.144; from 6.7 before 6.12.95; from 6.13 before 6.18.37; from 6.19 before 7.0.14; 7.1; and 1 more ranges	NVD

References

https://git.kernel.org/stable/c/7e9072dbd5f2f17934751873450d2c22080ead80patch
https://git.kernel.org/stable/c/21e87f336ac6303fed54a69b1d0d79a23b25c8d0patch
https://git.kernel.org/stable/c/3fd225f3e4cd67ec8ddab1afed9da03c7c43537cpatch
https://git.kernel.org/stable/c/1c4ffe6b4f04365485ed58d64c9bb86b46fc9037patch
https://git.kernel.org/stable/c/4bd8635f28c135a08aac6badcd7d9b5cdb34335fpatch
https://git.kernel.org/stable/c/5f4d2bd028ebb6e4c09a9d64842546022321d4a7patch
https://git.kernel.org/stable/c/0526931b16e5a118d367b7bfce7d797e63f7ac69patch
https://git.kernel.org/stable/c/6036b5067a8199ba7a2dc7b377d4b9dd276d5f9epatch

The CVE record on cve.org NVD's entry

The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.