cpuidle: Skip governor when only one idle state is available
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ dc2251bf98c66db3f4e055b751968f0871037ae4 · < 63ae78336f40bcd9a44952a7c6bafb9c88a8effd| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
On certain PowerNV systems without a power-management device-tree node, cpuidle can register only one idle state. If that state is a polling state, the ladder governor can select an out-of-bounds state and crash the system; the input does not describe an attacker trigger or access requirements.
Engineers running the Linux kernel on affected PowerNV systems should check their deployments; affected versions are not specified.