CVE-2026-64135: hwmon: (pmbus/adm1266) widen blackbox-info buffer to I2C_SMBUS_BLOCK_MAX
In the Linux kernel, the following vulnerability has been resolved:
hwmon: (pmbus/adm1266) widen blackbox-info buffer to I2CSMBUSBLOCKMAX
adm1266nvmemreadblackbox() declares a 5-byte stack buffer and passes it to i2csmbusreadblockdata() to retrieve the 4-byte BLACKBOXINFO response. i2csmbusreadblockdata() does not honour caller buffer sizes -- it memcpy()s data.block[0] bytes from the SMBus transaction (where data.block[0] is the length byte returned by the slave device, up to I2CSMBUSBLOCKMAX = 32):
memcpy(values, &data.block[1], data.block[0]);
If the device returns any block length above 5, the call overflows the caller's 5-byte stack buffer before the post-call
if (ret != 4) return -EIO;
check has a chance to reject the response.
Widen the local buffer to I2CSMBUSBLOCKMAX so the helper has room for any well-formed SMBus block response, matching the convention used by the other i2csmbusreadblockdata() callers in this driver.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Configuration
In hwmon: (pmbus/adm1266), widen the blackbox-info buffer used by adm1266_nvmem_read_blackbox() from a 5-byte stack buffer to I2C_SMBUS_BLOCK_MAX so memcpy() has room when data.block[0] (length byte) is up to 32.
Linux kernel (hwmon: pmbus/adm1266 blackbox-info handling) i2c_smbus_read_block_data() blackbox-info local buffer size = Widen to I2C_SMBUS_BLOCK_MAX (32)
Event History
Frequently Asked Questions
What is the severity of CVE-2026-64135?
CVE-2026-64135 has a risk rating of 44, indicating a moderate severity level.
How do I fix CVE-2026-64135?
To fix CVE-2026-64135, update your Linux kernel to the latest version where the vulnerability has been patched.
Which systems are affected by CVE-2026-64135?
CVE-2026-64135 affects the Linux kernel, specifically systems utilizing the hwmon subsystem with pmbus/adm1266.
What impact does CVE-2026-64135 have on system security?
CVE-2026-64135 could potentially allow for inappropriate data handling, leading to information disclosure.
Is there a workaround for CVE-2026-64135?
Currently, the recommended approach for CVE-2026-64135 is to apply the patch rather than relying on a workaround.