CVE-2026-64086: hwmon: (pmbus/adm1266) include PEC byte in pmbus_block_xfer read buffer
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 (crc != msgs[1].buf[msgs[1].buf[0] + 1])
read a byte beyond the array.
Bump the read_buf declaration to ADM1266_PMBUS_BLOCK_MAX + 2 so the
buffer can hold the length byte, up to 255 payload bytes, and the PEC
byte the i2c_msg length already accounts for.
Security readout for executives and security teams
Plain-English summary
CVE-2026-64086 is a Linux kernel memory overwrite in the ADM1266 PMBus hardware-monitoring driver. A maximum-length device response can make the kernel write one byte past a read buffer. The CVSS score is high, but the published vector requires local access and low privileges; no active exploitation is cited.
Executive priority
Treat as a high-priority kernel maintenance item for fleets using Linux on hardware that exposes ADM1266 PMBus monitoring. It is not cited as actively exploited, so prioritize by asset exposure and local-user risk rather than emergency internet-wide response.
Technical view
The adm1266 PMBus block read path allocates read_buf for length plus 255 data bytes, but configures I2C to receive length plus 255 data bytes plus PEC. A max-length response causes an out-of-bounds write and later out-of-bounds PEC read. Upstream resolves this by increasing read_buf to ADM1266_PMBUS_BLOCK_MAX + 2.
Likely exposure
Exposure is most likely on Linux systems using the adm1266 hwmon PMBus driver with affected kernel versions or downstream kernels lacking the referenced stable fixes. Systems without this driver, hardware path, or module loaded appear less likely to be exposed, based on the provided sources.
Exploitation context
The CVSS vector is local, low-complexity, low-privilege, no user interaction, with high confidentiality, integrity, and availability impact. The bundle says KEV is false and provides no cited evidence of active exploitation or public exploit availability.
Researcher notes
The core issue is a one-byte buffer overflow caused by mismatch between read_buf size and i2c_msg length when PEC is included. Evidence does not identify CWE, exploit primitives beyond the overflow, or affected distribution package versions.
Mitigation direction
Apply Linux kernel updates containing the referenced stable commits.
Use vendor kernel advisories for distribution-specific fixed package versions.
If update timing is constrained, assess whether the adm1266 driver is present and loaded.
Restrict local access to systems where vulnerable kernels cannot be updated promptly.
Validation and detection
Inventory kernel versions against the CVE affected-version data and vendor advisories.
Check whether the adm1266 PMBus hwmon driver is built, loaded, or required.
Confirm installed kernels include one of the referenced upstream stable fixes.
Track vendor advisories for backported fixes with different version strings.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2026-64086 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
0ADP providers
9Source links
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.