CVE-2026-64135: hwmon: (pmbus/adm1266) widen blackbox-info buffer to I2C_SMBUS_BLOCK_MAX

Published Jul 19, 2026
·
Updated

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

12 affected components
Linux Linux kernel
Linux Linux kernel>=5.10<5.10.258
Linux Linux kernel>=5.11<5.15.209
Linux Linux kernel>=5.16<6.1.175
Linux Linux kernel>=6.2<6.6.142
Linux Linux kernel>=6.7<6.12.92
Linux Linux kernel>=6.13<6.18.34
Linux Linux kernel>=6.19<7.0.11
Linux Linux kernel=7.1-rc1
Linux Linux kernel=7.1-rc2
Linux Linux kernel=7.1-rc3
Linux Linux kernel=7.1-rc4

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. 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

Jul 19, 2026
CVE Published
via MITRE·03:40 PM
Data Sourced
via MITRE·03:40 PM
Description
Data Sourced
via NVD·04:17 PM
RemedyDescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2026-64135?

CVE-2026-64135 has a risk rating of 44, indicating a moderate severity level.

2

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.

3

Which systems are affected by CVE-2026-64135?

CVE-2026-64135 affects the Linux kernel, specifically systems utilizing the hwmon subsystem with pmbus/adm1266.

4

What impact does CVE-2026-64135 have on system security?

CVE-2026-64135 could potentially allow for inappropriate data handling, leading to information disclosure.

5

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.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203