# CVE-2026-23332: linux: In the Linux kernel, the following vulnerability has been resolved:  cpufreq: intel_pstate: Fix crash during turbo di...

CVE-2026-23332 is fixed in 23 products on 1 platform, first by DEBIAN-CVE-2026-23332, released March 25, 2026. It is not reported as exploited. Patch Radar priority: Routine.

- Web page: https://patchblox.com/security/cve/CVE-2026-23332
- Priority: Routine
- CVSS: 5.5 (medium)
- EPSS: 0.0013
- CISA KEV: not listed
- Exploited (vendor report): no
- Publicly disclosed: no
- Published: Mar 25, 2026

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

## Where it's fixed

| Platform | Product | Fixed in | Fix | Released |
|---|---|---|---|---|
| Linux | bpftool6.18 amzn 2023 | 1:6.18.20-20.229.amzn2023 | [ALAS2023-2026-1596](https://patchblox.com/security/data/fix/linux/alas2023-2026-1596.md) | Apr 27, 2026 |
| Linux | bpftool6.18-debuginfo amzn 2023 | 1:6.18.20-20.229.amzn2023 | [ALAS2023-2026-1596](https://patchblox.com/security/data/fix/linux/alas2023-2026-1596.md) | Apr 27, 2026 |
| Linux | kernel-livepatch-6.18.20-20.229 amzn 2023 | 1:1.0-0.amzn2023 | [ALAS2023-2026-1596](https://patchblox.com/security/data/fix/linux/alas2023-2026-1596.md) | Apr 27, 2026 |
| Linux | kernel6.18 amzn 2023 | 1:6.18.20-20.229.amzn2023 | [ALAS2023-2026-1596](https://patchblox.com/security/data/fix/linux/alas2023-2026-1596.md) | Apr 27, 2026 |
| Linux | kernel6.18-debuginfo amzn 2023 | 1:6.18.20-20.229.amzn2023 | [ALAS2023-2026-1596](https://patchblox.com/security/data/fix/linux/alas2023-2026-1596.md) | Apr 27, 2026 |
| Linux | kernel6.18-debuginfo-common-aarch64 amzn 2023 | 1:6.18.20-20.229.amzn2023 | [ALAS2023-2026-1596](https://patchblox.com/security/data/fix/linux/alas2023-2026-1596.md) | Apr 27, 2026 |
| Linux | kernel6.18-debuginfo-common-x86_64 amzn 2023 | 1:6.18.20-20.229.amzn2023 | [ALAS2023-2026-1596](https://patchblox.com/security/data/fix/linux/alas2023-2026-1596.md) | Apr 27, 2026 |
| Linux | kernel6.18-devel amzn 2023 | 1:6.18.20-20.229.amzn2023 | [ALAS2023-2026-1596](https://patchblox.com/security/data/fix/linux/alas2023-2026-1596.md) | Apr 27, 2026 |
| Linux | kernel6.18-headers amzn 2023 | 1:6.18.20-20.229.amzn2023 | [ALAS2023-2026-1596](https://patchblox.com/security/data/fix/linux/alas2023-2026-1596.md) | Apr 27, 2026 |
| Linux | kernel6.18-libbpf amzn 2023 | 1:6.18.20-20.229.amzn2023 | [ALAS2023-2026-1596](https://patchblox.com/security/data/fix/linux/alas2023-2026-1596.md) | Apr 27, 2026 |
| Linux | kernel6.18-libbpf-debuginfo amzn 2023 | 1:6.18.20-20.229.amzn2023 | [ALAS2023-2026-1596](https://patchblox.com/security/data/fix/linux/alas2023-2026-1596.md) | Apr 27, 2026 |
| Linux | kernel6.18-libbpf-devel amzn 2023 | 1:6.18.20-20.229.amzn2023 | [ALAS2023-2026-1596](https://patchblox.com/security/data/fix/linux/alas2023-2026-1596.md) | Apr 27, 2026 |
| Linux | kernel6.18-libbpf-static amzn 2023 | 1:6.18.20-20.229.amzn2023 | [ALAS2023-2026-1596](https://patchblox.com/security/data/fix/linux/alas2023-2026-1596.md) | Apr 27, 2026 |
| Linux | kernel6.18-modules-extra amzn 2023 | 1:6.18.20-20.229.amzn2023 | [ALAS2023-2026-1596](https://patchblox.com/security/data/fix/linux/alas2023-2026-1596.md) | Apr 27, 2026 |
| Linux | kernel6.18-modules-extra-common amzn 2023 | 1:6.18.20-20.229.amzn2023 | [ALAS2023-2026-1596](https://patchblox.com/security/data/fix/linux/alas2023-2026-1596.md) | Apr 27, 2026 |
| Linux | kernel6.18-tools amzn 2023 | 1:6.18.20-20.229.amzn2023 | [ALAS2023-2026-1596](https://patchblox.com/security/data/fix/linux/alas2023-2026-1596.md) | Apr 27, 2026 |
| Linux | kernel6.18-tools-debuginfo amzn 2023 | 1:6.18.20-20.229.amzn2023 | [ALAS2023-2026-1596](https://patchblox.com/security/data/fix/linux/alas2023-2026-1596.md) | Apr 27, 2026 |
| Linux | kernel6.18-tools-devel amzn 2023 | 1:6.18.20-20.229.amzn2023 | [ALAS2023-2026-1596](https://patchblox.com/security/data/fix/linux/alas2023-2026-1596.md) | Apr 27, 2026 |
| Linux | linux Debian 14 | 6.19.8-1 | [DEBIAN-CVE-2026-23332](https://patchblox.com/security/data/fix/linux/debian-cve-2026-23332.md) | Mar 25, 2026 |
| Linux | perf6.18 amzn 2023 | 1:6.18.20-20.229.amzn2023 | [ALAS2023-2026-1596](https://patchblox.com/security/data/fix/linux/alas2023-2026-1596.md) | Apr 27, 2026 |
| Linux | perf6.18-debuginfo amzn 2023 | 1:6.18.20-20.229.amzn2023 | [ALAS2023-2026-1596](https://patchblox.com/security/data/fix/linux/alas2023-2026-1596.md) | Apr 27, 2026 |
| Linux | python3-perf6.18 amzn 2023 | 1:6.18.20-20.229.amzn2023 | [ALAS2023-2026-1596](https://patchblox.com/security/data/fix/linux/alas2023-2026-1596.md) | Apr 27, 2026 |
| Linux | python3-perf6.18-debuginfo amzn 2023 | 1:6.18.20-20.229.amzn2023 | [ALAS2023-2026-1596](https://patchblox.com/security/data/fix/linux/alas2023-2026-1596.md) | Apr 27, 2026 |

---

Data as of 2026-11-08T13:06:02Z UTC. Source: Patchblox Patch Radar (https://patchblox.com/security/patch-radar). Patchblox finds out-of-date software on Windows, macOS and Linux and updates it through release rings: https://patchblox.com/demo

Free to use with attribution: show "Data: Patchblox Patch Radar" with a link to https://patchblox.com/security/patch-radar. Terms, including what needs a written agreement: https://patchblox.com/security/patch-radar/use-the-data

Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.
