Answer in brief
CVE-2026-64086 records a Unknown severity vulnerability in hwmon: (pmbus/adm1266) include PEC byte in pmbus_block_xfer read buffer. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
Answer in brief
CVE-2026-64086 records a Unknown severity vulnerability in hwmon: (pmbus/adm1266) include PEC byte in pmbus_block_xfer read buffer. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=407dc802a9c0809ca6a48de4b4c63305eb84ef56 <397d3f523bfff2f4e3dacf9b1339bd76dc207f78 || >=407dc802a9c0809ca6a48de4b4c63305eb84ef56 <472744f69d25a2d5111ad62f1d62579dce2c13c8 || >=407dc802a9c0809ca6a48de4b4c63305eb84ef56 <528a9f88e88502d0c2f2052a279415074cd83715 || >=407dc802a9c0809ca6a48de4b4c63305eb84ef56 <d94ceb16e55b6d8019ab069e357c76ac42f0ffbc || >=407dc802a9c0809ca6a48de4b4c63305eb84ef56 <bd5be3fa5de6dbf61f1b3cec6b79c2c2f8065694 || >=407dc802a9c0809ca6a48de4b4c63305eb84ef56 <2279c342d94eca225bf9f301c8806a05a1c81619 || >=407dc802a9c0809ca6a48de4b4c63305eb84ef56 <a6c802145a8de0830bca803c6d415f7e9e683624 || >=407dc802a9c0809ca6a48de4b4c63305eb84ef56 <487566cb1ccdf3756fdd7bf8d875e612ff3169bb | 397d3f523bfff2f4e3dacf9b1339bd76dc207f78, 472744f69d25a2d5111ad62f1d62579dce2c13c8, 528a9f88e88502d0c2f2052a279415074cd83715, d94ceb16e55b6d8019ab069e357c76ac42f0ffbc, bd5be3fa5de6dbf61f1b3cec6b79c2c2f8065694, 2279c342d94eca225bf9f301c8806a05a1c81619, a6c802145a8de0830bca803c6d415f7e9e683624, 487566cb1ccdf3756fdd7bf8d875e612ff3169bb |
| Linux/Linuxgeneric | 5.10 | Not reported |
Published upstream
Jul 19, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=407dc802a9c0809ca6a48de4b4c63305eb84ef56 <397d3f523bfff2f4e3dacf9b1339bd76dc207f78 || >=407dc802a9c0809ca6a48de4b4c63305eb84ef56 <472744f69d25a2d5111ad62f1d62579dce2c13c8 || >=407dc802a9c0809ca6a48de4b4c63305eb84ef56 <528a9f88e88502d0c2f2052a279415074cd83715 || >=407dc802a9c0809ca6a48de4b4c63305eb84ef56 <d94ceb16e55b6d8019ab069e357c76ac42f0ffbc || >=407dc802a9c0809ca6a48de4b4c63305eb84ef56 <bd5be3fa5de6dbf61f1b3cec6b79c2c2f8065694 || >=407dc802a9c0809ca6a48de4b4c63305eb84ef56 <2279c342d94eca225bf9f301c8806a05a1c81619 || >=407dc802a9c0809ca6a48de4b4c63305eb84ef56 <a6c802145a8de0830bca803c6d415f7e9e683624 || >=407dc802a9c0809ca6a48de4b4c63305eb84ef56 <487566cb1ccdf3756fdd7bf8d875e612ff3169bb | 397d3f523bfff2f4e3dacf9b1339bd76dc207f78, 472744f69d25a2d5111ad62f1d62579dce2c13c8, 528a9f88e88502d0c2f2052a279415074cd83715, d94ceb16e55b6d8019ab069e357c76ac42f0ffbc, bd5be3fa5de6dbf61f1b3cec6b79c2c2f8065694, 2279c342d94eca225bf9f301c8806a05a1c81619, a6c802145a8de0830bca803c6d415f7e9e683624, 487566cb1ccdf3756fdd7bf8d875e612ff3169bb |
| Linux/Linuxgeneric | 5.10 | Not reported |
Published upstream
Jul 19, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.