Linux kernel task scheduling stall in scheduler class changes
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/core: Call wakeup_preempt() for queued tasks during class change
Paul reported recent RCU changes exposed a lost resched where CPU idles with a rcutorture thread waiting while being completely runnable.
Dumping the rq state at the time of idling with runnable tasks showed the following:
rq->next_class = &fair_sched_class rq->nr_running = 1 rq->cfs.h_nr_queued = 0 rq->rt.rt_nr_running = 1
Although the waiting task was an RT task, "rq->next_class" did not point to rt_sched_class and was stuck at the lower priority fair_sched_class.
Inspecting sched_change_end() revealed the following race with __sched_setscheduler() for queued, but non-running tasks:
CPU0 CPU1 ==== ====
From the CVE record · Linux
A race in the Linux kernel scheduler can leave a run queue pointing to the fair scheduling class after a queued, non-running task changes to a real-time class. The CPU can then idle even though that task is runnable. The input does not establish an attacker path, authentication requirement, or user interaction requirement.
Engineers running Linux kernels should check their versions against the vendor advisory; affected versions are not specified in the input.