CVE-2026-72397 (GCVE-0-2026-72397)
Vulnerability from cvelistv5
Published
2026-08-15 05:56
Modified
2026-08-17 05:43
Summary
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.
Impacted products
Vendor Product Version
Linux Linux Version: 068c227056b9223fea1a759e08db2558d5cbb5ad
Version: 068c227056b9223fea1a759e08db2558d5cbb5ad
Create a notification for this product.
Show details on NVD website


{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "drivers/hwmon/pmbus/pmbus_core.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "5bd0d47640395f8a8c34446b62d1781b88869dfa",
              "status": "affected",
              "version": "068c227056b9223fea1a759e08db2558d5cbb5ad",
              "versionType": "git"
            },
            {
              "lessThan": "828cd614e2af053ca5e1d6da767bbd8a1b5cabfb",
              "status": "affected",
              "version": "068c227056b9223fea1a759e08db2558d5cbb5ad",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "drivers/hwmon/pmbus/pmbus_core.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "4.3"
            },
            {
              "lessThan": "4.3",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "7.1.*",
              "status": "unaffected",
              "version": "7.1.5",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "7.2",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.1.5",
                  "versionStartIncluding": "4.3",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.2",
                  "versionStartIncluding": "4.3",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "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."
        }
      ],
      "metrics": [
        {
          "cvssV3_1": {
            "baseScore": 7.1,
            "baseSeverity": "HIGH",
            "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H",
            "version": "3.1"
          },
          "scenarios": [
            {
              "lang": "en",
              "value": "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."
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-08-17T05:43:39.708Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/5bd0d47640395f8a8c34446b62d1781b88869dfa"
        },
        {
          "url": "https://git.kernel.org/stable/c/828cd614e2af053ca5e1d6da767bbd8a1b5cabfb"
        }
      ],
      "title": "hwmon: (pmbus/core) honor vrm_version in pmbus_data2reg_vid()",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2026-72397",
    "datePublished": "2026-08-15T05:56:23.675Z",
    "dateReserved": "2026-08-09T03:40:39.924Z",
    "dateUpdated": "2026-08-17T05:43:39.708Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2"
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
  • Confirmed: The vulnerability is confirmed from an analyst perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
  • Patched: This vulnerability was successfully patched by the user reporting the sighting.
  • Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
  • Not confirmed: The user expresses doubt about the veracity of the vulnerability.
  • Not patched: This vulnerability was not successfully patched by the user reporting the sighting.


Loading…

Loading…