Vulnerability · Published Sep 17, 2026 · Assigned by Linux

CVE-2026-92492cpufreq/amd-pstate: handle missing policy in dynamic EPP callbacks

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: cpufreq/amd-pstate: handle missing policy in dynamic EPP callbacks cpufreq_cpu_get() returns NULL when no cpufreq policy is associated with the requested CPU, for example because the CPU is offline or the policy has already been torn down. Both amd_pstate_power_supply_notifier() and amd_pstate_profile_set() acquire a policy via cpufreq_cpu_get() and then pass that pointer to amd_pstate_get_balanced_epp() and amd_pstate_set_epp(), which dereference it unconditionally. A racing CPU hotplug or driver teardown can therefore lead to a NULL pointer dereference on either of these dynamic EPP paths. The third cpufreq_cpu_get() caller in this file, amd_pstate_verify(), already handles the NULL case. Bring the two new callers in line with that pattern: return NOTIFY_OK from the power-supply notifier (matching the other "nothing to do" exits) and -ENODEV from amd_pstate_profile_set() (the usual cpufreq error for a missing CPU policy). Found by code inspection; not tested on hardware.

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
Debian:14linux7.2.6-1DEBIAN-CVE-2026-92492
Ubuntu:22.04:LTSlinux-allwinner-5.19no fix listedUBUNTU-CVE-2026-92492
Ubuntu:22.04:LTSlinux-aws-5.19no fix listedUBUNTU-CVE-2026-92492
Ubuntu:24.04:LTSlinux-aws-6.14no fix listedUBUNTU-CVE-2026-92492
Ubuntu:24.04:LTSlinux-aws-6.17no fix listedUBUNTU-CVE-2026-92492
Ubuntu:22.04:LTSlinux-aws-6.2no fix listedUBUNTU-CVE-2026-92492
Ubuntu:22.04:LTSlinux-aws-6.5no fix listedUBUNTU-CVE-2026-92492
Ubuntu:22.04:LTSlinux-azure-5.19no fix listedUBUNTU-CVE-2026-92492
Ubuntu:24.04:LTSlinux-azure-6.11no fix listedUBUNTU-CVE-2026-92492
Ubuntu:24.04:LTSlinux-azure-6.14no fix listedUBUNTU-CVE-2026-92492
Ubuntu:24.04:LTSlinux-azure-6.17no fix listedUBUNTU-CVE-2026-92492
Ubuntu:22.04:LTSlinux-azure-6.2no fix listedUBUNTU-CVE-2026-92492
Ubuntu:22.04:LTSlinux-azure-6.5no fix listedUBUNTU-CVE-2026-92492
Ubuntu:22.04:LTSlinux-azure-fde-5.19no fix listedUBUNTU-CVE-2026-92492
Ubuntu:24.04:LTSlinux-azure-fde-6.14no fix listedUBUNTU-CVE-2026-92492
Ubuntu:24.04:LTSlinux-azure-fde-6.17no fix listedUBUNTU-CVE-2026-92492
Ubuntu:22.04:LTSlinux-azure-fde-6.2no fix listedUBUNTU-CVE-2026-92492
Ubuntu:24.04:LTSlinux-azure-nvidia-6.14no fix listedUBUNTU-CVE-2026-92492
Ubuntu:22.04:LTSlinux-gcp-5.19no fix listedUBUNTU-CVE-2026-92492
Ubuntu:24.04:LTSlinux-gcp-6.11no fix listedUBUNTU-CVE-2026-92492
Ubuntu:24.04:LTSlinux-gcp-6.14no fix listedUBUNTU-CVE-2026-92492
Ubuntu:24.04:LTSlinux-gcp-6.17no fix listedUBUNTU-CVE-2026-92492
Ubuntu:22.04:LTSlinux-gcp-6.2no fix listedUBUNTU-CVE-2026-92492
Ubuntu:22.04:LTSlinux-gcp-6.5no fix listedUBUNTU-CVE-2026-92492
Ubuntu:22.04:LTSlinux-hwe-5.19no fix listedUBUNTU-CVE-2026-92492
Ubuntu:24.04:LTSlinux-hwe-6.11no fix listedUBUNTU-CVE-2026-92492
Ubuntu:24.04:LTSlinux-hwe-6.14no fix listedUBUNTU-CVE-2026-92492
Ubuntu:22.04:LTSlinux-hwe-6.2no fix listedUBUNTU-CVE-2026-92492
Ubuntu:22.04:LTSlinux-hwe-6.5no fix listedUBUNTU-CVE-2026-92492
Ubuntu:22.04:LTSlinux-intel-iot-realtimeno fix listedUBUNTU-CVE-2026-92492
Ubuntu:22.04:LTSlinux-lowlatency-hwe-5.19no fix listedUBUNTU-CVE-2026-92492
Ubuntu:24.04:LTSlinux-lowlatency-hwe-6.11no fix listedUBUNTU-CVE-2026-92492
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.2no fix listedUBUNTU-CVE-2026-92492
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.5no fix listedUBUNTU-CVE-2026-92492
Ubuntu:24.04:LTSlinux-nvidia-6.11no fix listedUBUNTU-CVE-2026-92492
Ubuntu:24.04:LTSlinux-nvidia-6.17no fix listedUBUNTU-CVE-2026-92492
Ubuntu:22.04:LTSlinux-nvidia-6.2no fix listedUBUNTU-CVE-2026-92492
Ubuntu:22.04:LTSlinux-nvidia-6.5no fix listedUBUNTU-CVE-2026-92492
Ubuntu:22.04:LTSlinux-oem-5.17no fix listedUBUNTU-CVE-2026-92492
Ubuntu:22.04:LTSlinux-oem-6.0no fix listedUBUNTU-CVE-2026-92492
Ubuntu:22.04:LTSlinux-oem-6.1no fix listedUBUNTU-CVE-2026-92492
Ubuntu:24.04:LTSlinux-oem-6.11no fix listedUBUNTU-CVE-2026-92492
Ubuntu:24.04:LTSlinux-oem-6.14no fix listedUBUNTU-CVE-2026-92492
Ubuntu:22.04:LTSlinux-oem-6.5no fix listedUBUNTU-CVE-2026-92492
Ubuntu:24.04:LTSlinux-oem-6.8no fix listedUBUNTU-CVE-2026-92492
Ubuntu:24.04:LTSlinux-oracle-6.14no fix listedUBUNTU-CVE-2026-92492
Ubuntu:24.04:LTSlinux-oracle-6.17no fix listedUBUNTU-CVE-2026-92492
Ubuntu:22.04:LTSlinux-oracle-6.5no fix listedUBUNTU-CVE-2026-92492
Ubuntu:24.04:LTSlinux-raspi-realtimeno fix listedUBUNTU-CVE-2026-92492
Ubuntu:22.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-92492
Ubuntu:24.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-92492
Ubuntu:22.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2026-92492
Ubuntu:24.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2026-92492
Ubuntu:22.04:LTSlinux-riscv-5.19no fix listedUBUNTU-CVE-2026-92492
Ubuntu:24.04:LTSlinux-riscv-6.14no fix listedUBUNTU-CVE-2026-92492
Ubuntu:24.04:LTSlinux-riscv-6.17no fix listedUBUNTU-CVE-2026-92492
Ubuntu:22.04:LTSlinux-riscv-6.5no fix listedUBUNTU-CVE-2026-92492
Ubuntu:22.04:LTSlinux-starfive-5.19no fix listedUBUNTU-CVE-2026-92492
Ubuntu:22.04:LTSlinux-starfive-6.2no fix listedUBUNTU-CVE-2026-92492
Ubuntu:22.04:LTSlinux-starfive-6.5no fix listedUBUNTU-CVE-2026-92492

Affected products (as reported)

VendorProductVersions
Linux Linux 471d6659925aa0dcb4ab2520fa5ee3f49dfeab22 – before 70c8c8b50d80f681f50ddcc66a9400dd87508913e30ca6dd5345c5b8ba05f346a8e81105352fe571 – before f4ade8d224756ab69f108204dde6777bac4664e4e30ca6dd5345c5b8ba05f346a8e81105352fe571 – before 39c0cf62fc7851a17782e7efe8dfb2948739c681
Linux Linux 7.1

References