Vulnerability · Published May 27, 2026 · Assigned by Linux
CVE-2026-45968cpuidle: Skip governor when only one idle state is available
Medium 5.5
In plain English
A medium-severity security flaw in Linux from Linux. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.1% (higher than 3% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.
Official description
In the Linux kernel, the following vulnerability has been resolved: cpuidle: Skip governor when only one idle state is available On certain platforms (PowerNV systems without a power-mgt DT node), cpuidle may register only a single idle state. In cases where that single state is a polling state (state 0), the ladder governor may incorrectly treat state 1 as the first usable state and pass an out-of-bounds index. This can lead to a NULL enter callback being invoked, ultimately resulting in a system crash. [ 13.342636] cpuidle-powernv : Only Snooze is available [ 13.351854] Faulting instruction address: 0x00000000 [ 13.376489] NIP [0000000000000000] 0x0 [ 13.378351] LR [c000000001e01974] cpuidle_enter_state+0x2c4/0x668 Fix this by adding a bail-out in cpuidle_select() that returns state 0 directly when state_count <= 1, bypassing the governor and keeping the tick running.
Affected packages & fixed versions
| Ecosystem | Package | Fixed in | Advisory |
|---|---|---|---|
| Debian:12 | linux | 6.1.170-1 | DEBIAN-CVE-2026-45968 |
| Debian:13 | linux | 6.12.85-1 | DEBIAN-CVE-2026-45968 |
| Debian:14 | linux | 6.18.14-1 | DEBIAN-CVE-2026-45968 |
| Ubuntu:22.04:LTS | linux | 5.15.0-186.196 | UBUNTU-CVE-2026-45968 |
| Ubuntu:24.04:LTS | linux | 6.8.0-134.134 | UBUNTU-CVE-2026-45968 |
| Ubuntu:25.10 | linux | no fix listed | UBUNTU-CVE-2026-45968 |
| Ubuntu:22.04:LTS | linux-allwinner-5.19 | no fix listed | UBUNTU-CVE-2026-45968 |
| Ubuntu:22.04:LTS | linux-aws | 5.15.0-1112.119 | UBUNTU-CVE-2026-45968 |
| Ubuntu:24.04:LTS | linux-aws | 6.8.0-1060.63 | UBUNTU-CVE-2026-45968 |
| Ubuntu:25.10 | linux-aws | no fix listed | UBUNTU-CVE-2026-45968 |
| Ubuntu:22.04:LTS | linux-aws-5.19 | no fix listed | UBUNTU-CVE-2026-45968 |
| Ubuntu:24.04:LTS | linux-aws-6.14 | no fix listed | UBUNTU-CVE-2026-45968 |
| Ubuntu:24.04:LTS | linux-aws-6.17 | no fix listed | UBUNTU-CVE-2026-45968 |
| Ubuntu:22.04:LTS | linux-aws-6.2 | no fix listed | UBUNTU-CVE-2026-45968 |
| Ubuntu:22.04:LTS | linux-aws-6.5 | no fix listed | UBUNTU-CVE-2026-45968 |
| Ubuntu:22.04:LTS | linux-aws-6.8 | 6.8.0-1060.63~22.04.1 | UBUNTU-CVE-2026-45968 |
| Ubuntu:22.04:LTS | linux-azure | 5.15.0-1117.126 | UBUNTU-CVE-2026-45968 |
| Ubuntu:24.04:LTS | linux-azure | 6.8.0-1063.71 | UBUNTU-CVE-2026-45968 |
| Ubuntu:25.10 | linux-azure | no fix listed | UBUNTU-CVE-2026-45968 |
| Ubuntu:22.04:LTS | linux-azure-5.19 | no fix listed | UBUNTU-CVE-2026-45968 |
| Ubuntu:24.04:LTS | linux-azure-6.11 | no fix listed | UBUNTU-CVE-2026-45968 |
| Ubuntu:24.04:LTS | linux-azure-6.14 | no fix listed | UBUNTU-CVE-2026-45968 |
| Ubuntu:24.04:LTS | linux-azure-6.17 | no fix listed | UBUNTU-CVE-2026-45968 |
| Ubuntu:22.04:LTS | linux-azure-6.2 | no fix listed | UBUNTU-CVE-2026-45968 |
| Ubuntu:22.04:LTS | linux-azure-6.5 | no fix listed | UBUNTU-CVE-2026-45968 |
| Ubuntu:22.04:LTS | linux-azure-6.8 | 6.8.0-1063.71~22.04.1 | UBUNTU-CVE-2026-45968 |
| Ubuntu:22.04:LTS | linux-azure-fde | 5.15.0-1117.126 | UBUNTU-CVE-2026-45968 |
| Ubuntu:24.04:LTS | linux-azure-fde | 6.8.0-1062.69 | UBUNTU-CVE-2026-45968 |
| Ubuntu:25.10 | linux-azure-fde | no fix listed | UBUNTU-CVE-2026-45968 |
| Ubuntu:22.04:LTS | linux-azure-fde-5.19 | no fix listed | UBUNTU-CVE-2026-45968 |
| Ubuntu:24.04:LTS | linux-azure-fde-6.14 | no fix listed | UBUNTU-CVE-2026-45968 |
| Ubuntu:22.04:LTS | linux-azure-fde-6.2 | no fix listed | UBUNTU-CVE-2026-45968 |
| Ubuntu:22.04:LTS | linux-azure-fde-6.8 | 6.8.0-1062.69~22.04.1 | UBUNTU-CVE-2026-45968 |
| Ubuntu:24.04:LTS | linux-azure-nvidia | no fix listed | UBUNTU-CVE-2026-45968 |
| Ubuntu:24.04:LTS | linux-azure-nvidia-6.14 | no fix listed | UBUNTU-CVE-2026-45968 |
| Ubuntu:22.04:LTS | linux-gcp | 5.15.0-1112.122 | UBUNTU-CVE-2026-45968 |
| Ubuntu:24.04:LTS | linux-gcp | 6.8.0-1063.69 | UBUNTU-CVE-2026-45968 |
| Ubuntu:25.10 | linux-gcp | no fix listed | UBUNTU-CVE-2026-45968 |
| Ubuntu:22.04:LTS | linux-gcp-5.19 | no fix listed | UBUNTU-CVE-2026-45968 |
| Ubuntu:24.04:LTS | linux-gcp-6.11 | no fix listed | UBUNTU-CVE-2026-45968 |
| Ubuntu:24.04:LTS | linux-gcp-6.14 | no fix listed | UBUNTU-CVE-2026-45968 |
| Ubuntu:24.04:LTS | linux-gcp-6.17 | no fix listed | UBUNTU-CVE-2026-45968 |
| Ubuntu:22.04:LTS | linux-gcp-6.2 | no fix listed | UBUNTU-CVE-2026-45968 |
| Ubuntu:22.04:LTS | linux-gcp-6.5 | no fix listed | UBUNTU-CVE-2026-45968 |
| Ubuntu:22.04:LTS | linux-gcp-6.8 | 6.8.0-1063.69~22.04.1 | UBUNTU-CVE-2026-45968 |
| Ubuntu:22.04:LTS | linux-gke | 5.15.0-1108.114 | UBUNTU-CVE-2026-45968 |
| Ubuntu:24.04:LTS | linux-gke | 6.8.0-1058.64 | UBUNTU-CVE-2026-45968 |
| Ubuntu:22.04:LTS | linux-gkeop | 5.15.0-1095.103 | UBUNTU-CVE-2026-45968 |
| Ubuntu:24.04:LTS | linux-gkeop | 6.8.0-1045.48 | UBUNTU-CVE-2026-45968 |
| Ubuntu:22.04:LTS | linux-hwe-5.19 | no fix listed | UBUNTU-CVE-2026-45968 |
| Ubuntu:24.04:LTS | linux-hwe-6.11 | no fix listed | UBUNTU-CVE-2026-45968 |
| Ubuntu:24.04:LTS | linux-hwe-6.14 | no fix listed | UBUNTU-CVE-2026-45968 |
| Ubuntu:24.04:LTS | linux-hwe-6.17 | no fix listed | UBUNTU-CVE-2026-45968 |
| Ubuntu:22.04:LTS | linux-hwe-6.2 | no fix listed | UBUNTU-CVE-2026-45968 |
| Ubuntu:22.04:LTS | linux-hwe-6.5 | no fix listed | UBUNTU-CVE-2026-45968 |
| Ubuntu:22.04:LTS | linux-hwe-6.8 | 6.8.0-136.136~22.04.1 | UBUNTU-CVE-2026-45968 |
| Ubuntu:22.04:LTS | linux-ibm | 5.15.0-1106.110 | UBUNTU-CVE-2026-45968 |
| Ubuntu:24.04:LTS | linux-ibm | 6.8.0-1060.61 | UBUNTU-CVE-2026-45968 |
| Ubuntu:22.04:LTS | linux-ibm-6.8 | 6.8.0-1060.61~22.04.1 | UBUNTU-CVE-2026-45968 |
| Ubuntu:22.04:LTS | linux-intel-iot-realtime | no fix listed | UBUNTU-CVE-2026-45968 |
| Ubuntu:22.04:LTS | linux-intel-iotg | 5.15.0-1107.113 | UBUNTU-CVE-2026-45968 |
| Ubuntu:22.04:LTS | linux-kvm | 5.15.0-1104.109 | UBUNTU-CVE-2026-45968 |
| Ubuntu:22.04:LTS | linux-lowlatency | 5.15.0-184.194 | UBUNTU-CVE-2026-45968 |
| Ubuntu:24.04:LTS | linux-lowlatency | 6.8.0-134.134.1 | UBUNTU-CVE-2026-45968 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-5.19 | no fix listed | UBUNTU-CVE-2026-45968 |
| Ubuntu:24.04:LTS | linux-lowlatency-hwe-6.11 | no fix listed | UBUNTU-CVE-2026-45968 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.2 | no fix listed | UBUNTU-CVE-2026-45968 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.5 | no fix listed | UBUNTU-CVE-2026-45968 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.8 | 6.8.0-134.134.1~22.04.1 | UBUNTU-CVE-2026-45968 |
| Ubuntu:22.04:LTS | linux-nvidia | 5.15.0-1107.108 | UBUNTU-CVE-2026-45968 |
| Ubuntu:24.04:LTS | linux-nvidia | 6.8.0-1058.61 | UBUNTU-CVE-2026-45968 |
| Ubuntu:24.04:LTS | linux-nvidia-6.11 | no fix listed | UBUNTU-CVE-2026-45968 |
| Ubuntu:24.04:LTS | linux-nvidia-6.17 | no fix listed | UBUNTU-CVE-2026-45968 |
| Ubuntu:22.04:LTS | linux-nvidia-6.2 | no fix listed | UBUNTU-CVE-2026-45968 |
| Ubuntu:22.04:LTS | linux-nvidia-6.5 | no fix listed | UBUNTU-CVE-2026-45968 |
| Ubuntu:22.04:LTS | linux-nvidia-6.8 | 6.8.0-1058.61~22.04.1 | UBUNTU-CVE-2026-45968 |
| Ubuntu:24.04:LTS | linux-nvidia-lowlatency | 6.8.0-1058.61.1 | UBUNTU-CVE-2026-45968 |
| Ubuntu:22.04:LTS | linux-nvidia-tegra | 5.15.0-1064.66 | UBUNTU-CVE-2026-45968 |
| Ubuntu:24.04:LTS | linux-nvidia-tegra | 6.8.0-1029.30 | UBUNTU-CVE-2026-45968 |
| Ubuntu:22.04:LTS | linux-nvidia-tegra-igx | 5.15.0-1053.53 | UBUNTU-CVE-2026-45968 |
| Ubuntu:22.04:LTS | linux-oem-5.17 | no fix listed | UBUNTU-CVE-2026-45968 |
| Ubuntu:22.04:LTS | linux-oem-6.0 | no fix listed | UBUNTU-CVE-2026-45968 |
| Ubuntu:22.04:LTS | linux-oem-6.1 | no fix listed | UBUNTU-CVE-2026-45968 |
| Ubuntu:24.04:LTS | linux-oem-6.11 | no fix listed | UBUNTU-CVE-2026-45968 |
| Ubuntu:24.04:LTS | linux-oem-6.14 | no fix listed | UBUNTU-CVE-2026-45968 |
| Ubuntu:24.04:LTS | linux-oem-6.17 | no fix listed | UBUNTU-CVE-2026-45968 |
| Ubuntu:22.04:LTS | linux-oem-6.5 | no fix listed | UBUNTU-CVE-2026-45968 |
| Ubuntu:24.04:LTS | linux-oem-6.8 | no fix listed | UBUNTU-CVE-2026-45968 |
| Ubuntu:22.04:LTS | linux-oracle | 5.15.0-1109.115 | UBUNTU-CVE-2026-45968 |
| Ubuntu:24.04:LTS | linux-oracle | 6.8.0-1057.58 | UBUNTU-CVE-2026-45968 |
| Ubuntu:25.10 | linux-oracle | no fix listed | UBUNTU-CVE-2026-45968 |
| Ubuntu:24.04:LTS | linux-oracle-6.14 | no fix listed | UBUNTU-CVE-2026-45968 |
| Ubuntu:24.04:LTS | linux-oracle-6.17 | no fix listed | UBUNTU-CVE-2026-45968 |
| Ubuntu:22.04:LTS | linux-oracle-6.5 | no fix listed | UBUNTU-CVE-2026-45968 |
| Ubuntu:22.04:LTS | linux-oracle-6.8 | 6.8.0-1057.58~22.04.1 | UBUNTU-CVE-2026-45968 |
| Ubuntu:22.04:LTS | linux-raspi | 5.15.0-1106.109 | UBUNTU-CVE-2026-45968 |
| Ubuntu:24.04:LTS | linux-raspi | 6.8.0-1060.64 | UBUNTU-CVE-2026-45968 |
| Ubuntu:25.10 | linux-raspi | no fix listed | UBUNTU-CVE-2026-45968 |
| Ubuntu:24.04:LTS | linux-raspi-realtime | no fix listed | UBUNTU-CVE-2026-45968 |
| Ubuntu:22.04:LTS | linux-realtime | no fix listed | UBUNTU-CVE-2026-45968 |
| Ubuntu:24.04:LTS | linux-realtime | no fix listed | UBUNTU-CVE-2026-45968 |
| Ubuntu:25.10 | linux-realtime | no fix listed | UBUNTU-CVE-2026-45968 |
| Ubuntu:22.04:LTS | linux-riscv | no fix listed | UBUNTU-CVE-2026-45968 |
| Ubuntu:24.04:LTS | linux-riscv | no fix listed | UBUNTU-CVE-2026-45968 |
| Ubuntu:25.10 | linux-riscv | no fix listed | UBUNTU-CVE-2026-45968 |
| Ubuntu:22.04:LTS | linux-riscv-5.19 | no fix listed | UBUNTU-CVE-2026-45968 |
| Ubuntu:24.04:LTS | linux-riscv-6.14 | no fix listed | UBUNTU-CVE-2026-45968 |
| Ubuntu:24.04:LTS | linux-riscv-6.17 | no fix listed | UBUNTU-CVE-2026-45968 |
| Ubuntu:22.04:LTS | linux-riscv-6.5 | no fix listed | UBUNTU-CVE-2026-45968 |
| Ubuntu:22.04:LTS | linux-riscv-6.8 | 6.8.0-134.134~22.04.1 | UBUNTU-CVE-2026-45968 |
| Ubuntu:22.04:LTS | linux-starfive-5.19 | no fix listed | UBUNTU-CVE-2026-45968 |
| Ubuntu:22.04:LTS | linux-starfive-6.2 | no fix listed | UBUNTU-CVE-2026-45968 |
| Ubuntu:22.04:LTS | linux-starfive-6.5 | no fix listed | UBUNTU-CVE-2026-45968 |
| Ubuntu:24.04:LTS | linux-xilinx | 6.8.0-1032.33 | UBUNTU-CVE-2026-45968 |
| Ubuntu:22.04:LTS | linux-xilinx-zynqmp | 5.15.0-1075.79 | UBUNTU-CVE-2026-45968 |
Affected products (as reported)
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | dc2251bf98c66db3f4e055b751968f0871037ae4 – before a0f7e804edc82e513d1ccb7c95ed8b351522ec81dc2251bf98c66db3f4e055b751968f0871037ae4 – before 5d103a38e2ae96eca57fd17161bcd29bd4622d1cdc2251bf98c66db3f4e055b751968f0871037ae4 – before 4da2b897283c39980d6ae09dc1560fcd937879e5dc2251bf98c66db3f4e055b751968f0871037ae4 – before 5c577ac939bca486cb02069505cfe47a5312ce02dc2251bf98c66db3f4e055b751968f0871037ae4 – before 8f6833d919bae915ead6c599a53e81e19b32da52dc2251bf98c66db3f4e055b751968f0871037ae4 – before 63ae78336f40bcd9a44952a7c6bafb9c88a8effddc2251bf98c66db3f4e055b751968f0871037ae4 – before a0724e40a58a0e323c59707edeae5b71d15800dcdc2251bf98c66db3f4e055b751968f0871037ae4 – before e5c9ffc6ae1bcdb1062527d611043681ac301aca |
| Linux | Linux | 4.14 |
References
- https://git.kernel.org/stable/c/a0f7e804edc82e513d1ccb7c95ed8b351522ec81
- https://git.kernel.org/stable/c/5d103a38e2ae96eca57fd17161bcd29bd4622d1c
- https://git.kernel.org/stable/c/4da2b897283c39980d6ae09dc1560fcd937879e5
- https://git.kernel.org/stable/c/5c577ac939bca486cb02069505cfe47a5312ce02
- https://git.kernel.org/stable/c/8f6833d919bae915ead6c599a53e81e19b32da52
- https://git.kernel.org/stable/c/63ae78336f40bcd9a44952a7c6bafb9c88a8effd
- https://git.kernel.org/stable/c/a0724e40a58a0e323c59707edeae5b71d15800dc
- https://git.kernel.org/stable/c/e5c9ffc6ae1bcdb1062527d611043681ac301aca