{"api_version":"1","generated_at":"2026-08-18T13:35:38+00:00","cve":"CVE-2026-72397","urls":{"html":"https://cve.report/CVE-2026-72397","api":"https://cve.report/api/cve/CVE-2026-72397.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-72397","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-72397"},"summary":{"title":"hwmon: (pmbus/core) honor vrm_version in pmbus_data2reg_vid()","description":"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.","state":"PUBLISHED","assigner":"Linux","published_at":"2026-08-15 06:22:13","updated_at":"2026-08-17 06:19:06"},"problem_types":[],"metrics":[{"version":"3.1","source":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","type":"Secondary","score":"7.1","severity":"HIGH","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H","data":{"version":"3.1","vectorString":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H","baseScore":7.1,"baseSeverity":"HIGH","attackVector":"LOCAL","attackComplexity":"LOW","privilegesRequired":"LOW","userInteraction":"NONE","scope":"UNCHANGED","confidentialityImpact":"NONE","integrityImpact":"HIGH","availabilityImpact":"HIGH"}},{"version":"3.1","source":"CNA","type":"DECLARED","score":"7.1","severity":"HIGH","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H","data":{"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"}}],"references":[{"url":"https://git.kernel.org/stable/c/828cd614e2af053ca5e1d6da767bbd8a1b5cabfb","name":"https://git.kernel.org/stable/c/828cd614e2af053ca5e1d6da767bbd8a1b5cabfb","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/5bd0d47640395f8a8c34446b62d1781b88869dfa","name":"https://git.kernel.org/stable/c/5bd0d47640395f8a8c34446b62d1781b88869dfa","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-72397","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-72397","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 068c227056b9223fea1a759e08db2558d5cbb5ad 5bd0d47640395f8a8c34446b62d1781b88869dfa git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 068c227056b9223fea1a759e08db2558d5cbb5ad 828cd614e2af053ca5e1d6da767bbd8a1b5cabfb git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 4.3","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 4.3 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.1.5 7.1.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.2 * original_commit_for_fix","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":{"cve_year":"2026","cve_id":"72397","cve":"CVE-2026-72397","epss":"0.001510000","percentile":"0.048150000","score_date":"2026-08-17","updated_at":"2026-08-18 00:11:47"},"legacy_qids":[]},"source_records":{"cve_program":{"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—writable hwmon sysfs attributes (pmbus_set_sensor) and the PMBus regulator set_voltage path (pmbus_regulator_set_voltage)—which 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"},"nvd":{"publishedDate":"2026-08-15 06:22:13","lastModifiedDate":"2026-08-17 06:19:06","problem_types":[],"metrics":{"cvssMetricV31":[{"source":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","type":"Secondary","cvssData":{"version":"3.1","vectorString":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H","baseScore":7.1,"baseSeverity":"HIGH","attackVector":"LOCAL","attackComplexity":"LOW","privilegesRequired":"LOW","userInteraction":"NONE","scope":"UNCHANGED","confidentialityImpact":"NONE","integrityImpact":"HIGH","availabilityImpact":"HIGH"},"exploitabilityScore":1.8,"impactScore":5.2}]},"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"72397","Ordinal":"1","Title":"hwmon: (pmbus/core) honor vrm_version in pmbus_data2reg_vid()","CVE":"CVE-2026-72397","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"72397","Ordinal":"1","NoteData":"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.","Type":"Description","Title":"hwmon: (pmbus/core) honor vrm_version in pmbus_data2reg_vid()"}]}}}