Vulnerability · Published Sep 17, 2026 · Assigned by Linux

CVE-2026-90136platform/x86/amd/hsmp: Reject negative power cap writes in hwmon

Unrated

In plain English

A security flaw in Linux from Linux. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.2% (higher than 11% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS )–Not rated
Exploit odds (30 days)0.2%top 89.2% of all CVEs
Exploited in the wildNo reportsnot in CISA KEV
Attack toolingNoneno public tooling known

Official description

In the Linux kernel, the following vulnerability has been resolved: platform/x86/amd/hsmp: Reject negative power cap writes in hwmon hsmp_hwmon_write() takes the user-supplied hwmon value as a signed long and assigns "val / MICROWATT_PER_MILLIWATT" to msg.args[0], which is a __u32. MICROWATT_PER_MILLIWATT is an unsigned long, so a negative write to power1_cap (e.g. "echo -1 > power1_cap") is first converted to a huge unsigned value by the division and then stored into the u32 argument. As a result a nonsensical, multi-gigawatt socket power limit is sent to the SMU via HSMP_SET_SOCKET_POWER_LIMIT instead of the write being rejected. Reject negative values with -EINVAL before the conversion. Tested with HSMP enabled: CAP=$(dirname $(grep -l amd_hsmp_hwmon \ /sys/class/hwmon/hwmon*/name | head -1))/power1_cap # negative write echo -1000000 > $CAP ; echo "ret=$?" # valid positive write must still work echo 400000000 > $CAP ; echo "ret=$?" Before: # echo -1000000 > $CAP ; echo "ret=$?" ret=0 <- accepted; bogus limit sent to SMU # echo 400000000 > $CAP ; echo "ret=$?" ret=0 After: # echo -1000000 > $CAP ; echo "ret=$?" bash: echo: write error: Invalid argument ret=1 <- rejected with -EINVAL # echo 400000000 > $CAP ; echo "ret=$?" ret=0 <- valid write still works

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
Debian:14linux7.2.6-1DEBIAN-CVE-2026-90136
Ubuntu:26.04:LTSlinux7.0.0-42.42UBUNTU-CVE-2026-90136
Ubuntu:22.04:LTSlinux-allwinner-5.19no fix listedUBUNTU-CVE-2026-90136
Ubuntu:26.04:LTSlinux-aws7.0.0-1016.17UBUNTU-CVE-2026-90136
Ubuntu:22.04:LTSlinux-aws-5.19no fix listedUBUNTU-CVE-2026-90136
Ubuntu:24.04:LTSlinux-aws-6.14no fix listedUBUNTU-CVE-2026-90136
Ubuntu:24.04:LTSlinux-aws-6.17no fix listedUBUNTU-CVE-2026-90136
Ubuntu:22.04:LTSlinux-aws-6.2no fix listedUBUNTU-CVE-2026-90136
Ubuntu:22.04:LTSlinux-aws-6.5no fix listedUBUNTU-CVE-2026-90136
Ubuntu:24.04:LTSlinux-aws-7.0no fix listedUBUNTU-CVE-2026-90136
Ubuntu:26.04:LTSlinux-azureno fix listedUBUNTU-CVE-2026-90136
Ubuntu:22.04:LTSlinux-azure-5.19no fix listedUBUNTU-CVE-2026-90136
Ubuntu:24.04:LTSlinux-azure-6.11no fix listedUBUNTU-CVE-2026-90136
Ubuntu:24.04:LTSlinux-azure-6.14no fix listedUBUNTU-CVE-2026-90136
Ubuntu:24.04:LTSlinux-azure-6.17no fix listedUBUNTU-CVE-2026-90136
Ubuntu:22.04:LTSlinux-azure-6.2no fix listedUBUNTU-CVE-2026-90136
Ubuntu:22.04:LTSlinux-azure-6.5no fix listedUBUNTU-CVE-2026-90136
Ubuntu:24.04:LTSlinux-azure-7.0no fix listedUBUNTU-CVE-2026-90136
Ubuntu:26.04:LTSlinux-azure-fdeno fix listedUBUNTU-CVE-2026-90136
Ubuntu:22.04:LTSlinux-azure-fde-5.19no fix listedUBUNTU-CVE-2026-90136
Ubuntu:24.04:LTSlinux-azure-fde-6.14no fix listedUBUNTU-CVE-2026-90136
Ubuntu:24.04:LTSlinux-azure-fde-6.17no fix listedUBUNTU-CVE-2026-90136
Ubuntu:22.04:LTSlinux-azure-fde-6.2no fix listedUBUNTU-CVE-2026-90136
Ubuntu:24.04:LTSlinux-azure-fde-7.0no fix listedUBUNTU-CVE-2026-90136
Ubuntu:24.04:LTSlinux-azure-nvidia-6.14no fix listedUBUNTU-CVE-2026-90136
Ubuntu:26.04:LTSlinux-gcp7.0.0-1016.18UBUNTU-CVE-2026-90136
Ubuntu:22.04:LTSlinux-gcp-5.19no fix listedUBUNTU-CVE-2026-90136
Ubuntu:24.04:LTSlinux-gcp-6.11no fix listedUBUNTU-CVE-2026-90136
Ubuntu:24.04:LTSlinux-gcp-6.14no fix listedUBUNTU-CVE-2026-90136
Ubuntu:24.04:LTSlinux-gcp-6.17no fix listedUBUNTU-CVE-2026-90136
Ubuntu:22.04:LTSlinux-gcp-6.2no fix listedUBUNTU-CVE-2026-90136
Ubuntu:22.04:LTSlinux-gcp-6.5no fix listedUBUNTU-CVE-2026-90136
Ubuntu:24.04:LTSlinux-gcp-7.0no fix listedUBUNTU-CVE-2026-90136
Ubuntu:26.04:LTSlinux-gkeno fix listedUBUNTU-CVE-2026-90136
Ubuntu:22.04:LTSlinux-hwe-5.19no fix listedUBUNTU-CVE-2026-90136
Ubuntu:24.04:LTSlinux-hwe-6.11no fix listedUBUNTU-CVE-2026-90136
Ubuntu:24.04:LTSlinux-hwe-6.14no fix listedUBUNTU-CVE-2026-90136
Ubuntu:24.04:LTSlinux-hwe-6.17no fix listedUBUNTU-CVE-2026-90136
Ubuntu:22.04:LTSlinux-hwe-6.2no fix listedUBUNTU-CVE-2026-90136
Ubuntu:22.04:LTSlinux-hwe-6.5no fix listedUBUNTU-CVE-2026-90136
Ubuntu:24.04:LTSlinux-hwe-7.07.0.0-42.42~24.04.1UBUNTU-CVE-2026-90136
Ubuntu:26.04:LTSlinux-ibm7.0.0-1017.17UBUNTU-CVE-2026-90136
Ubuntu:22.04:LTSlinux-intel-iot-realtimeno fix listedUBUNTU-CVE-2026-90136
Ubuntu:22.04:LTSlinux-lowlatency-hwe-5.19no fix listedUBUNTU-CVE-2026-90136
Ubuntu:24.04:LTSlinux-lowlatency-hwe-6.11no fix listedUBUNTU-CVE-2026-90136
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.2no fix listedUBUNTU-CVE-2026-90136
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.5no fix listedUBUNTU-CVE-2026-90136
Ubuntu:26.04:LTSlinux-nvidiano fix listedUBUNTU-CVE-2026-90136
Ubuntu:24.04:LTSlinux-nvidia-6.11no fix listedUBUNTU-CVE-2026-90136
Ubuntu:24.04:LTSlinux-nvidia-6.17no fix listedUBUNTU-CVE-2026-90136
Ubuntu:22.04:LTSlinux-nvidia-6.2no fix listedUBUNTU-CVE-2026-90136
Ubuntu:22.04:LTSlinux-nvidia-6.5no fix listedUBUNTU-CVE-2026-90136
Ubuntu:24.04:LTSlinux-nvidia-7.0no fix listedUBUNTU-CVE-2026-90136
Ubuntu:26.04:LTSlinux-nvidia-bosno fix listedUBUNTU-CVE-2026-90136
Ubuntu:22.04:LTSlinux-oem-5.17no fix listedUBUNTU-CVE-2026-90136
Ubuntu:22.04:LTSlinux-oem-6.0no fix listedUBUNTU-CVE-2026-90136
Ubuntu:22.04:LTSlinux-oem-6.1no fix listedUBUNTU-CVE-2026-90136
Ubuntu:24.04:LTSlinux-oem-6.11no fix listedUBUNTU-CVE-2026-90136
Ubuntu:24.04:LTSlinux-oem-6.14no fix listedUBUNTU-CVE-2026-90136
Ubuntu:24.04:LTSlinux-oem-6.17no fix listedUBUNTU-CVE-2026-90136
Ubuntu:22.04:LTSlinux-oem-6.5no fix listedUBUNTU-CVE-2026-90136
Ubuntu:24.04:LTSlinux-oem-6.8no fix listedUBUNTU-CVE-2026-90136
Ubuntu:26.04:LTSlinux-oem-7.07.0.0-1017.17UBUNTU-CVE-2026-90136
Ubuntu:26.04:LTSlinux-oracle7.0.0-1015.16UBUNTU-CVE-2026-90136
Ubuntu:24.04:LTSlinux-oracle-6.14no fix listedUBUNTU-CVE-2026-90136
Ubuntu:24.04:LTSlinux-oracle-6.17no fix listedUBUNTU-CVE-2026-90136
Ubuntu:22.04:LTSlinux-oracle-6.5no fix listedUBUNTU-CVE-2026-90136
Ubuntu:24.04:LTSlinux-oracle-7.0no fix listedUBUNTU-CVE-2026-90136
Ubuntu:26.04:LTSlinux-raspino fix listedUBUNTU-CVE-2026-90136
Ubuntu:24.04:LTSlinux-raspi-realtimeno fix listedUBUNTU-CVE-2026-90136
Ubuntu:22.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-90136
Ubuntu:24.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-90136
Ubuntu:26.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-90136
Ubuntu:22.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2026-90136
Ubuntu:24.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2026-90136
Ubuntu:26.04:LTSlinux-riscv7.0.0-42.42.1UBUNTU-CVE-2026-90136
Ubuntu:22.04:LTSlinux-riscv-5.19no fix listedUBUNTU-CVE-2026-90136
Ubuntu:24.04:LTSlinux-riscv-6.14no fix listedUBUNTU-CVE-2026-90136
Ubuntu:24.04:LTSlinux-riscv-6.17no fix listedUBUNTU-CVE-2026-90136
Ubuntu:22.04:LTSlinux-riscv-6.5no fix listedUBUNTU-CVE-2026-90136
Ubuntu:24.04:LTSlinux-riscv-7.07.0.0-42.42.1~24.04.1UBUNTU-CVE-2026-90136
Ubuntu:22.04:LTSlinux-starfive-5.19no fix listedUBUNTU-CVE-2026-90136
Ubuntu:22.04:LTSlinux-starfive-6.2no fix listedUBUNTU-CVE-2026-90136
Ubuntu:22.04:LTSlinux-starfive-6.5no fix listedUBUNTU-CVE-2026-90136

Affected products (as reported)

VendorProductVersions
Linux Linux 92c025db52bb94a032eb3d473bb81e62c19ddbd3 – before 2c09cadec116eba3fdbcb5d8d8641f6777d4a11f92c025db52bb94a032eb3d473bb81e62c19ddbd3 – before 1b0a3d915320f1600e5ff43f8bc21b73118480b892c025db52bb94a032eb3d473bb81e62c19ddbd3 – before 3921bb8635ff2836622df1cdf3194d4f3c1835a4
Linux Linux 6.16

References