hwmon: (pmbus/adm1266) include PEC byte in pmbus_block_xfer read buffer
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 407dc802a9c0809ca6a48de4b4c63305eb84ef56 · < 2279c342d94eca225bf9f301c8806a05a1c81619| No fix yet |
| Linux 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 (crc != msgs[1].buf[msgs[1].buf[0] + 1])
From the CVE record · Linux
The Linux kernel’s adm1266 PMBus driver allocates a read buffer one byte too small for a maximum-length response with a PEC byte. Under that response condition, the I2C controller can write one byte past the buffer, and a subsequent PEC check can read past it. The input does not establish whether an attacker can trigger this condition or whether authentication or user interaction is required.
Engineers running Linux kernels with the adm1266 PMBus driver should check their versions against the vendor advisory; affected versions were not provided.