SECUFOCUSNOW
Home›CVE index›CVE-2026-64086
Review reviewHigh

CVE-2026-64086

Linux

In the Linux kernel, the following vulnerability has been resolved: hwmon: (pmbus/adm1266) include PEC byte in pmbus_block_xfer read buffer adm1266_pmbus_block_xfer() sets up the read transaction with .buf = data->read_buf, .len = ADM1266_PMBUS_BLOCK_MAX + 2, but read_buf in struct adm1266_data is declared as u8 read_buf[ADM1266_PMBUS_BLOCK_MAX + 1]; For a max-length block response (length byte = 255 + up to 1 PEC byte), the i2c controller is told to write 257 bytes into a 256-byte buffer, putting one byte past the end of read_buf. The same response also makes the subsequent PEC compare if...

CVSS
7.8
EPSS
-
- percentile
CISA KEV
Not listed
Published
2026.07.20
PRIORITY ASSESSMENT

Review review

The CVSS severity warrants an early asset and exposure review.

Known exploitationNot established by KEV
Exploit probability-
Technical severityCVSS 7.8

Vulnerability overview

In the Linux kernel, the following vulnerability has been resolved: hwmon: (pmbus/adm1266) include PEC byte in pmbus_block_xfer read buffer adm1266_pmbus_block_xfer() sets up the read transaction with .buf = data->read_buf, .len = ADM1266_PMBUS_BLOCK_MAX + 2, but read_buf in struct adm1266_data is declared as u8 read_buf[ADM1266_PMBUS_BLOCK_MAX + 1]; For a max-length block response (length byte = 255 + up to 1 PEC byte), the i2c controller is told to write 257 bytes into a 256-byte buffer, putting one byte past the end of read_buf. The same response also makes the subsequent PEC compare if...

Affected product and versions

Product
Linux
Affected versions
>= 407dc802a9c0809ca6a48de4b4c63305eb84ef56 < 397d3f523bfff2f4e3dacf9b1339bd76dc207f78, >= 407dc802a9c0809ca6a48de4b4c63305eb84ef56 < 472744f69d25a2d5111ad62f1d62579dce2c13c8, >= 407dc802a9c0809ca6a48de4b4c63305eb84ef56 < 528a9f88e88502d0c2f2052a279415074cd83715, >= 407dc802a9c0809ca6a48de4b4c63305eb84ef56 < d94ceb16e55b6d8019ab069e357c76ac42f0ffbc, >= 407dc802a9c0809ca6a48de4b4c63305eb84ef56 < bd5be3fa5de6dbf61f1b3cec6b79c2c2f8065694, >= 407dc802a9c0809ca6a48de4b4c63305eb84ef56 < 2279c342d94eca225bf9f301c8806a05a1c81619, >= 407dc802a9c0809ca6a48de4b4c63305eb84ef56 < a6c802145a8de0830bca803c6d415f7e9e683624, >= 407dc802a9c0809ca6a48de4b4c63305eb84ef56 < 487566cb1ccdf3756fdd7bf8d875e612ff3169bb, >= 5.10
Fixed versions
No verified fixed-version field is available yet

Recommended response sequence

Confirm exposure before applying a vendor-supported change.

Full remediation guide
  1. 1
    Identify

    Confirm that Linux and an affected version are present.

  2. 2
    Prioritize

    Combine exploitation signals with asset exposure and business criticality.

  3. 3
    Remediate

    Follow the vendor advisory or supported update path and preserve rollback options.

  4. 4
    Verify

    Recheck the version, service health, access paths, and relevant logs.

Technical data

CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CWE
Not available