sched_ext: Don't warn on core-sched forced idle in put_prev_task_scx()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
sched_ext: Don't warn on core-sched forced idle in put_prev_task_scx()
put_prev_task_scx() warns when a runnable task drops to a lower sched_class without SCX_OPS_ENQ_LAST, on the assumption that balance_one() would have kept it running. Core scheduling breaks that: a forced-idle SMT sibling reschedules through the core_pick fast path in pick_next_task(), which skips pick_task_scx() and thus balance_one(), so a runnable task can drop to idle with ENQ_LAST unset.
Gate the warning on sched_cpu_cookie_match(): a cookie mismatch means core scheduling forced the idle, while a match (or core scheduling off) still catches a genuine missing-ENQ_LAST drop.
From the CVE record · Linux
The Linux kernel's sched_ext scheduler can emit an incorrect warning when core scheduling forces an SMT sibling idle and a runnable task drops to idle. The input describes no attacker capability, access requirement, or user interaction; the issue occurs when a scheduling cookie mismatch causes the core-pick path to skip the usual balancing check.
Engineers running the Linux kernel with sched_ext and core scheduling should check their versions; affected versions were not provided.