hwmon: (pmbus/core) honor vrm_version in pmbus_data2reg_vid()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
hwmon: (pmbus/core) honor vrm_version in pmbus_data2reg_vid()
pmbus_data2reg_vid() hardcoded the VR11 encoding regardless of the vrm_version configured by the driver, while pmbus_reg2data_vid() already switched on it. Any driver that selects a non-VR11 VID mode and exposes a regulator (or hwmon vout setter) sent dangerously wrong codes to PMBUS_VOUT_COMMAND -- e.g. an nvidia195mv part asked for 200 mV got the VR11 clamp to 500 mV encoded as 0xB2, which the chip interprets as 1080 mV.
Mirror pmbus_reg2data_vid() so writes round-trip with reads.
From the CVE record · Linux
The Linux kernel's PMBus core used VR11 encoding for voltage writes even when a driver selected a different VID mode. On affected drivers that expose a regulator or hwmon voltage setter, a voltage request can send a dangerously incorrect command to the device. The input does not specify an attacker, access requirements, or user-interaction conditions.
Engineers running Linux kernels with PMBus drivers that select a non-VR11 VID mode and expose a regulator or hwmon voltage setter should check their kernel versions against the advisory.