PT-2026-27697 · Linux · Linux
Published
2026-03-25
·
Updated
2026-03-25
·
CVE-2026-23332
None
No severity ratings or metrics are available. When they are, we'll update the corresponding info on the page.
In the Linux kernel, the following vulnerability has been resolved:
cpufreq: intel pstate: Fix crash during turbo disable
When the system is booted with kernel command line argument "nosmt" or
"maxcpus" to limit the number of CPUs, disabling turbo via:
echo 1 > /sys/devices/system/cpu/intel pstate/no turbo
results in a crash:
PF: supervisor read access in kernel mode
PF: error code(0x0000) - not-present page
PGD 0 P4D 0
Oops: Oops: 0000 [#1] SMP PTI
...
RIP: 0010:store no turbo+0x100/0x1f0
...
This occurs because for each possible cpu() returns CPUs even if they
are not online. For those CPUs, all cpu data[] will be NULL. Since
commit 973207ae3d7c ("cpufreq: intel pstate: Rearrange max frequency
updates handling code"), all cpu data[] is dereferenced even for CPUs
which are not online, causing the NULL pointer dereference.
To fix that, pass CPU number to intel pstate update max freq() and use
all cpu data[] for those CPUs for which there is a valid cpufreq policy.
Found an issue in the description? Have something to add? Feel free to write us 👾
Related Identifiers
Affected Products
Linux