CVE-2026-64373
Last modified
CVE-2026-64373 is a medium-severity vulnerability rated 4.7/10 on the CVSS scale. 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(). EPSS estimates a 0.18% chance of exploitation in the next 30 days.
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 ]
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux Kernel | >= 4.4.198, < 4.5 |
| Linux | Linux Kernel | >= 4.9.198, < 4.10 |
| Linux | Linux Kernel | >= 4.14.151, < 4.15 |
| Linux | Linux Kernel | >= 4.19.81, < 4.20 |
| Linux | Linux Kernel | >= 5.3.8, < 5.4 |
| Linux | Linux Kernel | >= 5.4.1, < 5.10.261 |
| Linux | Linux Kernel | >= 5.11, < 5.15.212 |
| Linux | Linux Kernel | >= 5.16, < 6.1.178 |
| Linux | Linux Kernel | >= 6.2, < 6.6.145 |
| Linux | Linux Kernel | >= 6.7, < 6.12.96 |
| Linux | Linux Kernel | >= 6.13, < 6.18.39 |
| Linux | Linux Kernel | >= 6.19, < 7.1.4 |
| Linux | Linux Kernel | 5.4 |
References
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2026-64373?
How severe is CVE-2026-64373?
How do I fix CVE-2026-64373?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-64368In the Linux kernel, the following vulnerability has been re…8.1
- CVE-2026-64369In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-6437Improper neutralization of argument delimiters in the volume…6.9
- CVE-2026-64370In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-64371In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-64372In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-64374In the Linux kernel, the following vulnerability has been re…7.5
- CVE-2026-64375In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-64376In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-64377In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-64378In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-64379In the Linux kernel, the following vulnerability has been re…7.1
Are you affected by CVE-2026-64373?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
