CVE-2026-90364: ACPI: processor: Unregister cpufreq notifier on init failure
ACPI: processor: Unregister cpufreq notifier on init failure
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 6.6.157.1-1 - Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 6.1.176-1Fixed in 6.1.190-1Fixed in 6.12.115-2Fixed in 7.2.12-1Fixed in 7.2.15-1 - Upgrade
Upgrade
debian/linux-6.12to a version that resolves this vulnerability.Fixed in 6.12.113-1~deb12u1 - 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 - Compensating control
On ACPI processor initialization failure after the cpufreq policy notifier has been registered, unregister the cpufreq notifier to mirror the module exit path; this applies when driver_register() or cpuhp_setup_state() fails.
Event History
Frequently Asked Questions
Under what conditions can this issue occur?
It can occur only when ACPI processor driver initialization fails after the cpufreq policy notifier has been registered, specifically if ACPI processor driver registration or CPU hotplug state setup fails.
What is left behind when initialization fails?
The cpufreq policy notifier remains registered despite the failed initialization. The corrected error path unregisters that notifier, matching the module exit cleanup behavior.
How can I determine whether a system is exposed?
Review the Linux kernel source or applied stable patches to determine whether the ACPI processor initialization failure path unregisters the cpufreq notifier. The provided references identify the fixes.