CVE-2026-23332
Last modified
CVE-2026-23332 is a medium-severity vulnerability rated 5.5/10 on the CVSS scale. 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. EPSS estimates a 0.12% chance of exploitation in the next 30 days.
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.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Linux | Linux Kernel | >= 6.16.1, < 6.18.17 | — |
| Linux | Linux Kernel | >= 6.19, < 6.19.7 | — |
| Linux | Linux Kernel | 6.16 | — |
| Linux | Linux Kernel | 7.0 | Rc1 |
References
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2026-23332?
How severe is CVE-2026-23332?
How do I fix CVE-2026-23332?
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-23327In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2026-23328In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-23329In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-2333Improper Neutralization of Special Elements used in a Comman…9.8
- CVE-2026-23330In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-23331In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-23333Rejected reason: This CVE ID has been rejected or withdrawn …
- CVE-2026-23334In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-23335In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-23336In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-23337In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-23338In the Linux kernel, the following vulnerability has been re…5.5
Are you affected by CVE-2026-23332?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
