sched_ext: Fix stale direct dispatch state in ddsp_dsq_id
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel ca685511f7afd42cdcbb0feea42e5d332d384251, Kernel 6.18.22, Kernel 6.19.12 and 4 more.
In the Linux kernel, the following vulnerability has been resolved: sched_ext: Fix stale direct dispatch state in ddsp_dsq_id @p->scx.ddsp_dsq_id can be left set (non-SCX_DSQ_INVALID) triggering a spurious warning in mark_direct_dispatch() when the next wakeup's ops.select_cpu() calls scx_bpf_dsq_insert(), such as: WARNING: kernel/sched/ext.c:1273 at scx_dsq_insert_commit+0xcd/0x140 The root cause is that ddsp_dsq_id was only cleared in dispatch_enqueue(), which is not reached in all paths that consume or cancel a direct dispatch verdict. Fix it by clearing it at the right places: - direct_dispatch(): cache the direct dispatch state in local variables and clear it before dispatch_enqueue() on the synchronous path. For the deferred path, the direct dispatch state must remain set until process_ddsp_deferred_locals() consumes them. - process_ddsp_deferred_locals(): cache the dispatch state in local variables and clear it before calling dispatch_to_local_dsq(), which may migrate the task to another rq. - do_enqueue_task(): clear the dispatch state on the enqueue path (local/global/bypass fallbacks), where the direct dispatch verdict is ignored. - dequeue_task_scx(): clear the dispatch state after dispatch_dequeue() to handle both the deferred dispatch cancellation and the holding_cpu race, covering all cases where a pending direct dispatch is cancelled. - scx_disable_task(): clear the direct dispatch state when transitioning a task out of the current scheduler. Waking tasks may have had the direct dispatch state set by the outgoing scheduler's ops.select_cpu() and then been queued on a wake_list via ttwu_queue_wakelist(), when SCX_OPS_ALLOW_QUEUED_WAKEUP is set. Such tasks are not on the runqueue and are not iterated by scx_bypass(), so their direct dispatch state won't be cleared. Without this clear, any subsequent SCX scheduler that tries to direct dispatch the task will trigger the WARN_ON_ONCE() in mark_direct_dispatch().
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | >=5b26f7b920f76b2b9cc398c252a9e35e44bf5bb9 <ca685511f7afd42cdcbb0feea42e5d332d384251, >=6.13 <6.18.22, >=6.19 <6.19.12, =7.0, >=5b26f7b920f76b2b9cc398c252a9e35e44bf5bb9 <7e0ffb72de8aa3b25989c2d980e81b829c577010, >=5b26f7b920f76b2b9cc398c252a9e35e44bf5bb9 <7ea601daa0153e19cd1c6e6b300348c70c05fe77, >=6.12 <6.12.82, =6.12, >=5b26f7b920f76b2b9cc398c252a9e35e44bf5bb9 <5e7b2cc8fae9ec2a5bc53311191d2faaff75a4b5 | ca685511f7afd42cdcbb0feea42e5d332d384251, 6.18.22, 6.19.12, 7e0ffb72de8aa3b25989c2d980e81b829c577010, 7ea601daa0153e19cd1c6e6b300348c70c05fe77, 6.12.82, 5e7b2cc8fae9ec2a5bc53311191d2faaff75a4b5 |
| linux-kernel: Kernel | >=6.12.0 <6.12.82, >=6.13.0 <6.18.22, >=6.19.0 <6.19.12 | 6.12.82, 6.18.22, 6.19.12 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket