{
  "schema_version": "1.6.1",
  "id": "RPI-CVE-2026-72397",
  "modified": "2026-10-09T11:39:44Z",
  "upstream": [
    "CVE-2026-72397"
  ],
  "published": "2026-08-15T06:04:33Z",
  "summary": "hwmon: (pmbus/core) honor vrm_version in pmbus_data2reg_vid()",
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nhwmon: (pmbus/core) honor vrm_version in pmbus_data2reg_vid()\n\npmbus_data2reg_vid() hardcoded the VR11 encoding regardless of the\nvrm_version configured by the driver, while pmbus_reg2data_vid()\nalready switched on it. Any driver that selects a non-VR11 VID mode\nand exposes a regulator (or hwmon vout setter) sent dangerously\nwrong codes to PMBUS_VOUT_COMMAND -- e.g. an nvidia195mv part asked\nfor 200 mV got the VR11 clamp to 500 mV encoded as 0xB2, which the\nchip interprets as 1080 mV.\n\nMirror pmbus_reg2data_vid() so writes round-trip with reads.",
  "severity": [
    {
      "type": "CVSS_V3",
      "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H"
    }
  ],
  "affected": [
    {
      "package": {
        "ecosystem": "Raspberry Pi OS:12",
        "name": "linux"
      },
      "versions": [
        "1:6.1.47-1+rpt4"
      ],
      "ecosystem_specific": {
        "binaries": [
          {
            "binary_name": "linux-image-6.1.0-rpi3-rpi-2712",
            "binary_version": "1:6.1.47-1+rpt4"
          },
          {
            "binary_name": "linux-image-6.1.0-rpi3-rpi-v6",
            "binary_version": "1:6.1.47-1+rpt4"
          },
          {
            "binary_name": "linux-image-6.1.0-rpi3-rpi-v7",
            "binary_version": "1:6.1.47-1+rpt4"
          },
          {
            "binary_name": "linux-image-6.1.0-rpi3-rpi-v7l",
            "binary_version": "1:6.1.47-1+rpt4"
          },
          {
            "binary_name": "linux-image-6.1.0-rpi3-rpi-v8",
            "binary_version": "1:6.1.47-1+rpt4"
          }
        ]
      },
      "database_specific": {
        "per_version": {
          "1:6.1.47-1+rpt4": {
            "linux_commit": "655fc658a15ae7a6f37103754adb39ba52a9a14e",
            "upstream_version": "6.1.47",
            "assessment": "commit ancestry (strak rule)",
            "upstream_fixed": null,
            "compiled_filter": false
          }
        }
      }
    }
  ],
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-72397"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/5bd0d47640395f8a8c34446b62d1781b88869dfa"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/828cd614e2af053ca5e1d6da767bbd8a1b5cabfb"
    }
  ],
  "database_specific": {
    "source": "https://git.kernel.org/pub/scm/linux/security/vulns.git",
    "upstream_modified": "2026-08-17T05:50:24Z",
    "severity": {
      "source": "kernel CNA",
      "cvss_v3_score": 7.1,
      "cvss_v3_severity": "High",
      "scenario": "AV:L - The bug is only reached from local host interfaces\u2014writable hwmon sysfs attributes (pmbus_set_sensor) and the PMBus regulator set_voltage path (pmbus_regulator_set_voltage)\u2014which encode values and issue I2C PMBUS_VOUT_COMMAND writes; there is no network, adjacent-radio, or direct physical-access entry point.\nAC:L - On systems with non-VR11 VID PMBus controllers (VR12/VR13/IMVP9/AMD/nvidia195mv), any voltage-setting write deterministically uses the wrong VR11 encoding with no race, timing window, or uncontrollable memory layout; the attacker fully controls the written millivolt value and can repeat the operation reliably.\nPR:L - Writable hwmon limit attributes are exposed as mode 0644 with no capability check in pmbus_set_sensor, so a local uid-0 context (including user-namespace root or container root with /sys access) can drive the bad encoding; regulator consumers can also be influenced from ordinary local workloads on affected server/GPU platforms.\nUI:N - Exploitation requires only the attacker (or attacker-controlled software) to write hwmon voltage limits or invoke regulator voltage changes; no separate victim interaction such as plugging hardware or approving a prompt is needed.\nS:U - Impact is confined to misprogramming PMBus voltage rails on the same host kernel authority; it does not cross VM, IOMMU, or sandbox boundaries and is not a guest-to-host escape.\nC:N - This is a write-side VID encoding logic error, not kernel memory corruption; reads use the correct pmbus_reg2data_vid path and the flaw does not disclose kernel pointers, arbitrary memory, or other confidential data.\nI:H - Incorrect VID-to-register conversion sends dangerously wrong PMBUS_VOUT_COMMAND values to hardware (e.g., 200 mV requested on nvidia195mv becomes 1080 mV applied), corrupting critical CPU/GPU/board power-rail configuration and potentially causing permanent hardware damage.\nA:H - Severe over- or under-voltage on core power rails can trigger immediate hardware protection shutdowns, system hangs/resets, and sustained denial of service on data-center, HPC, and GPU server deployments using affected PMBus VRM controllers."
    }
  }
}