Cloudanix VulnDB

CVE-2026-92493

None

CVSS

—

EPSS

0.2%

Published

Sep 17, 2026

CISA due date

—

Cloudanix analysis

Schedule a fix SSVC: Track

A test tool meant only for certain AMD processors can accidentally crash the whole computer if someone tries to run it on the wrong kind of processor.

Exploitation
Local Privilege
Attacker needs
Local User
Complexity
Trivial
Impact
Denial Of Service
Component
OS kernel
Class
Improper Input Validation
Remediation
Upgrade
Effort
Medium
Patch risk
Low

What it actually does

Missing platform check allows the amd_pstate_ut test module to execute code paths that dereference NULL pointers when loaded on non-AMD systems, resulting in a kernel oops.

Why it matters to the business

Accidental or malicious loading of the test module on unsupported hardware can crash the entire system, causing denial of service and requiring manual intervention or reboot.

How an attack unfolds

An attacker with the ability to load kernel modules runs modprobe amd_pstate_ut on an Intel or other non-AMD platform; the missing driver-state guard lets the test code reach a NULL pointer access inside amd_pstate_ut_check_perf, triggering an unhandled page fault and kernel panic.

How to fix it

Apply the upstream patch that adds explicit state detection before running any amd-pstate unit tests; rebuild and deploy the fixed kernel; avoid loading amd_pstate_ut on non-AMD platforms until the fix is present.

How to confirm the fix worked

Confirm the patched amd_pstate_ut_init performs an early active-driver check and returns without executing test code on non-AMD systems; attempt module load on both AMD and non-AMD hardware and verify no NULL dereference occurs.

Typical attack path

  1. Obtain ability to execute modprobe or insmod as root
  2. Load amd_pstate_ut module on a non-AMD system
  3. Trigger amd_pstate_ut_init which calls unchecked perf test routine
  4. Kernel dereferences NULL pointer at amd_pstate_ut_check_perf+0x141
  5. System panics with oops and may enter kdump or reboot

How to detect it

Search kernel logs for the exact oops signature containing amd_pstate_ut_check_perf and NULL pointer dereference at address 0000000000000080; inspect module load history for amd_pstate_ut on non-AMD CPUs.

  • BUG: kernel NULL pointer dereference, address: 0000000000000080
  • RIP: amd_pstate_ut_check_perf
  • amd_pstate_ut: 1 amd_pstate_ut_acpi_cpc_valid
  • modprobe.*amd_pstate_ut

What your security team should do

  • Prioritize kernel update on all systems that may receive the amd_pstate_ut module
  • Restrict module loading via allow-lists or signed-module enforcement
  • Add boot-time or CI checks that refuse to load the test module on non-AMD hardware
  • Monitor EPSS and KEV status; no immediate exploitation observed

The record

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)

Affected packages

Ecosystem Package Introduced Fixed