cpufreq: intel_pstate: Fix crash during turbo disable
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.
- Products
- Kernel
- Affected versions
- Not specified
- Fixed versions
- 6.18.17, 6.19.7
- CVEs
- CVE-2026-23332
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 4 Nov 2026, 20:52 UTC · Revision 1
Source evidence
cpufreq: intel_pstate: Fix crash during turbo disable
core-osv · Original sourcePublished 25 Mar 2026, 10:27 UTC
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.
osv:CVE-2026-23332
Kernel
Fixed versions: 6.18.17, 6.19.7
Complete source record
{
"id": "1b2ec8408a6885e03a432c9cbb189968c0fcb8feb36f4e7d41865fd3dd8879fd",
"url": "https://osv.dev/vulnerability/CVE-2026-23332",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "cpufreq: intel_pstate: Fix crash during turbo disable",
"summary": "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.",
"evidence": "osv:CVE-2026-23332",
"products": [
{
"name": {
"value": "Kernel",
"evidence": "/affected/1/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "6.18.17",
"evidence": "/affected/1/ranges"
},
{
"value": "6.19.7",
"evidence": "/affected/1/ranges"
}
],
"affected_versions": []
}
],
"severity": "unknown",
"structured": {
"id": "CVE-2026-23332",
"aliases": [
"CVE-2026-23332"
],
"affected": [
{
"ranges": [
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "973207ae3d7c3c92df4a382df5d7bd695deaa904"
},
{
"fixed": "a1850e2aef4d15405e7ff53fd51c4b3124d46182"
},
{
"fixed": "d20d48916ce8531b157c2edeba76d69af2974270"
},
{
"fixed": "6b050482ec40569429d963ac52afa878691b04c9"
}
]
}
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-23332.json"
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.16.0"
},
{
"fixed": "6.18.17"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.19.0"
},
{
"fixed": "6.19.7"
}
]
}
],
"package": {
"name": "Kernel",
"ecosystem": "Linux"
},
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-23332.json"
}
}
],
"modified": "2026-10-28T02:30:39.555621659Z",
"provider": "osv",
"references": [
"https://git.kernel.org/stable/c/6b050482ec40569429d963ac52afa878691b04c9",
"https://git.kernel.org/stable/c/a1850e2aef4d15405e7ff53fd51c4b3124d46182",
"https://git.kernel.org/stable/c/d20d48916ce8531b157c2edeba76d69af2974270",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/23xxx/CVE-2026-23332.json",
"https://nvd.nist.gov/vuln/detail/CVE-2026-23332",
"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
],
"provider_metadata": {
"cna_assigner": "Linux",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/23xxx/CVE-2026-23332.json"
}
},
"related_cves": [
{
"value": "CVE-2026-23332",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": null
},
"source_id": "core-osv",
"document_id": 506899,
"published_at": "2026-03-25T10:27:23.193+00:00"
}