CVE-2026-64373: Linux kernel · cpufreq: Fix hotplug-suspend race during reboot
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in cd4524ff6567fa4458a5bec4b017105e671d393e : update Linux kernel when convenient.
Data as of 6 Nov 2026, 17:04 UTC
Rated by Threat Radar · No CVSS score from NVD or the CNA
Thin evidence
One scorer or none- CISA SSVC
- Exploitation
- No evidence of active exploitation and no public proof of concept
- Automatable
- Attackers cannot reliably automate steps 1–4 of the kill chain
- Technical impact
- Limited control over the software or limited information exposure
CISA SSVC assessment, 2026-11-06.
- Patch
- Available – fixed in cd4524ff6567fa4458a5bec4b017105e671d393e, a9029dd55696c651ee46912afa2a166fa456bb3e, a0106b41f9a724868d390b8b3b4ea5ca0e04ea53 +10
Exploitation evidence
Disclosed: evidence found.
CVE published 25 Jul 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 6 Nov 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
Description
In the Linux kernel, the following vulnerability has been resolved: cpufreq: Fix hotplug-suspend race during reboot During system reboot, cpufreq_suspend() is called via the kernel_restart() -> device_shutdown() path. Unlike the normal system suspend path, the reboot path does not call freeze_processes(), so userspace processes and kernel threads remain active. This allows CPU hotplug operations to run concurrently with cpufreq_suspend(). The original code has no synchronization with CPU hotplug, leading to a race condition where governor_data can be freed by the hotplug path while cpufreq_suspend() is still accessing it, resulting in a null pointer dereference: Unable to handle kernel NULL pointer dereference Call Trace: do_kernel_fault+0x28/0x3c cpufreq_suspend+0xdc/0x160 device_shutdown+0x18/0x200 kernel_restart+0x40/0x80 arm64_sys_reboot+0x1b0/0x200 Fix this by adding cpus_read_lock()/cpus_read_unlock() to cpufreq_suspend() to block CPU hotplug operations while suspend is in progress. [ rjw: Changelog edits ]
References
- git.kernel.org/stable/c/6d5dd354c37abaf4d60400c55c71f23ba2b33639 (opens in a new tab)
- git.kernel.org/stable/c/9103078c7b3091a2fbb52af176f95982ee7dd7f8 (opens in a new tab)
- git.kernel.org/stable/c/cd4524ff6567fa4458a5bec4b017105e671d393e (opens in a new tab)
- git.kernel.org/stable/c/73255d702c7560185fd5951aadcf7eb057c2f453 (opens in a new tab)
- git.kernel.org/stable/c/a0ef2fc89d28ca62923376c4b8ffaa57136a36be (opens in a new tab)
- git.kernel.org/stable/c/6e175c00c62dca3d91b987015808b5d52e8db2b4 (opens in a new tab)
- git.kernel.org/stable/c/a0106b41f9a724868d390b8b3b4ea5ca0e04ea53 (opens in a new tab)
- git.kernel.org/stable/c/a9029dd55696c651ee46912afa2a166fa456bb3e (opens in a new tab)