CVE-2026-64373

CVE CVE-2026-64373EUVD EUVD-2026-48917Published 2026-07-25T08:50:25.000Z

What the advisory describes

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 ]

Source: EUVD (ENISA), in the words of the advisory.

Products the advisory names

These come from the advisory itself, not from any check we performed.

Linux — Linux 65650b35133ff20f0c9ef0abd5c3c66dbce3ae57 <6e175c00c62dca3d91b987015808b5d52e8db2b4; 65650b35133ff20f0c9ef0abd5c3c66dbce3ae57 <a9029dd55696c651ee46912afa2a166fa456bb3e; 5.4; 65650b35133ff20f0c9ef0abd5c3c66dbce3ae57 <a0106b41f9a724868d390b8b3b4ea5ca0e04ea53; 5f466713989250938624afa79dc33bae20920700; 8bfa06ea6e81bf08d2132d7e70c2b5313b34caf8; patch: 6.1.178; 65650b35133ff20f0c9ef0abd5c3c66dbce3ae57 <6d5dd354c37abaf4d60400c55c71f23ba2b33639; 4.4.198 <4.5; patch: 7.1.4; 4.19.81 <4.20; 65650b35133ff20f0c9ef0abd5c3c66dbce3ae57 <9103078c7b3091a2fbb52af176f95982ee7dd7f8; patch: 5.10.261; patch: 6.12.96; 7ccf3b8b7a12dc9da158c2e699c36d04b2496944; 5.3.8 <5.4; patch: 6.6.145; patch: 0; cb4b4601f910c78d2b49f637a12ef98b41cb76a9; 4.9.198 <4.10; 4.14.151 <4.15; patch: 7.2-rc1; 65650b35133ff20f0c9ef0abd5c3c66dbce3ae57 <73255d702c7560185fd5951aadcf7eb057c2f453; 89ab39da1452d272007acc5912d4008047b86706; patch: 5.15.212; patch: 6.18.39; 65650b35133ff20f0c9ef0abd5c3c66dbce3ae57 <a0ef2fc89d28ca62923376c4b8ffaa57136a36be; 65650b35133ff20f0c9ef0abd5c3c66dbce3ae57 <cd4524ff6567fa4458a5bec4b017105e671d393e

The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.

Carried in the product catalogue

An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.

Linux — Linux

Does this concern one of your customers?

This page cannot answer that — it does not know your estate. Whoever has recorded their environments gets the answer the morning after publication, together with a paragraph they can forward to the customer unedited.

Try it for 28 days

Patchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.