CVE-2026-92493: cpufreq: amd-pstate-ut: Skip tests when amd-pstate driver is not active
cpufreq: amd-pstate-ut: Skip tests when amd-pstate driver is not active
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
ubuntu/linux-hwe-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-42.42~24.04.1 - Upgrade
Upgrade
ubuntu/linux-riscv-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-42.42.1~24.04.1 - Upgrade
Upgrade
ubuntu/linuxto a version that resolves this vulnerability.Fixed in 7.0.0-42.42 - Upgrade
Upgrade
ubuntu/linux-awsto a version that resolves this vulnerability.Fixed in 7.0.0-1016.17 - Upgrade
Upgrade
ubuntu/linux-gcpto a version that resolves this vulnerability.Fixed in 7.0.0-1016.18 - Upgrade
Upgrade
ubuntu/linux-ibmto a version that resolves this vulnerability.Fixed in 7.0.0-1017.17 - Upgrade
Upgrade
ubuntu/linux-oem-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-1017.17 - Upgrade
Upgrade
ubuntu/linux-oracleto a version that resolves this vulnerability.Fixed in 7.0.0-1015.16 - Upgrade
Upgrade
ubuntu/linux-riscvto a version that resolves this vulnerability.Fixed in 7.0.0-42.42.1
Event History
Frequently Asked Questions
Which systems are exposed to the reported crash?
Systems where the amd_pstate_ut module is loaded while the amd-pstate driver is not active are exposed. The reported case is loading it with modprobe on an Intel platform.
What action triggers the issue?
Loading the amd_pstate_ut module can trigger a kernel NULL pointer dereference when its tests run without an active amd-pstate driver. The crash occurred during module initialization in the reported trace.
Does normal AMD P-State operation need to be enabled for this issue to occur?
The issue is specifically caused by the unit-test module testing when the amd-pstate driver is not active. The resolution adds driver-state detection so the tests are skipped in that condition.