Skip to main content
VulnerabilityPublished Updated

CVE-2026-23332: Linux kernel · cpufreq: intel_pstate: Fix crash during turbo disable

Affects Linux kernelSource CVE Database V5

0
Compare

Not known to be exploited · fixed in d20d48916ce8531b157c2edeba76d69af2974270 : update Linux kernel when convenient.

Data as of 5 Nov 2026, 22:04 UTC

Severity
Unrated

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-05.

Patch
Available – fixed in d20d48916ce8531b157c2edeba76d69af2974270, a1850e2aef4d15405e7ff53fd51c4b3124d46182, 6b050482ec40569429d963ac52afa878691b04c9

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 25 Mar 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 5 Nov 2026.

What to do

Upgrade Linux kernel to d20d48916ce8531b157c2edeba76d69af2974270, a1850e2aef4d15405e7ff53fd51c4b3124d46182 or 6b050482ec40569429d963ac52afa878691b04c9.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 973207ae3d7c3c92df4a382df5d7bd695deaa904, < d20d48916ce8531b157c2edeba76d69af2974270
Fixed in
  • d20d48916ce8531b157c2edeba76d69af2974270
LinuxLinuxAffected
  • ≥ 973207ae3d7c3c92df4a382df5d7bd695deaa904, < a1850e2aef4d15405e7ff53fd51c4b3124d46182
Fixed in
  • a1850e2aef4d15405e7ff53fd51c4b3124d46182
LinuxLinuxAffected
  • ≥ 973207ae3d7c3c92df4a382df5d7bd695deaa904, < 6b050482ec40569429d963ac52afa878691b04c9
Fixed in
  • 6b050482ec40569429d963ac52afa878691b04c9
LinuxLinuxAffected
  • =6.16
Fixed in–

Description

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.

References

Community reviews

Loading reviews…