GPU VulnDB

Database/Kernel, userspace & hypervisor

Linux kernel adm1266 hwmon: PMBus block read buffer one byte short, i2c write and PEC compare overrun

CVE-2026-64086Kernel, userspace & hypervisorcurated

Impact

adm1266_pmbus_block_xfer() tells the i2c controller it may write ADM1266_PMBUS_BLOCK_MAX + 2 bytes into read_buf, which is declared one byte smaller. A maximum-length block response with a PEC byte therefore puts one byte past the end of the buffer inside struct adm1266_data, and the following PEC comparison reads one byte past it as well. Same hardware-to-host boundary as the other adm1266 fixes in this batch, and a much smaller corruption - a single adjacent byte in a driver structure - but it is still an out-of-bounds kernel write driven by the device's answer. Only relevant on boards carrying the ADM1266 with the driver built and loaded. Distinct code path and distinct fix from CVE-2026-64084 and CVE-2026-64085, so it is listed on its own.

Who can reach it

Requires a malicious or malfunctioning ADM1266 on the board's PMBus segment returning a maximum-length block response, together with a local operation that triggers a block read - root-level sysfs/nvmem access on the host. No network path, no tenant path.

What to do

Pick up the fix in a stable kernel (commits linked in the record) and reboot each affected node, draining GPU workloads first. The record names no vendor advisory or fixed release beyond the upstream commits. Not building or not loading the adm1266 module removes the exposure where the chip is not monitored.

References

Related entries

All Kernel, userspace & hypervisor entries

This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.