https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Tue, 29 Sep 2026 08:44:08 +0000 https://vulnerability.circl.lu/vuln/cve-2026-89518 <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>sched_ext: Fix this_rq() assumptions in dispatch kfuncs</p> <p>Under core scheduling, dispatch runs from within the core-wide pick and can target a sibling rq, so ops.dispatch() may execute on a CPU different from the dispatched rq&#39;s. Several kfunc paths assumed the two always coincide:</p> <p>- scx_dsq_move() decided whether an rq lock is held by testing this_rq()&#39;s rq flags and lock-danced accordingly. A dispatch for a sibling took the unlocked-context branch and acquired the source rq lock on top of the already held dispatched rq lock which could deadlock.</p> <p>- scx_bpf_sub_dispatch() dispatched this_rq() with its stashed sub_dispatch_prev, which is NULL when dispatching for a sibling.</p> <p>- finish_dispatch(), scx_bpf_dsq_reenq() and scx_bpf_dsq_nr_queued() resolved SCX_DSQ_LOCAL to this CPU&#39;s local DSQ rather than the dispatched rq&#39;s. The latter two are callable from other rq-locked operations too, where SCX_DSQ_LOCAL now likewise resolves to the op&#39;s rq. This changes behavior also without core scheduling, e.g. for ops.enqueue() running a remote wakeup on the waking CPU, and is intended: which CPU happens to execute an operation is incidental, the op&#39;s rq is what it is operating on, and the resolution now matches the insert side where SCX_DSQ_LOCAL dispatches land on the task&#39;s rq.</p> <p>Use the rq tracked by scx_locked_rq(), which is set to the dispatched rq around ops invocations and NULL in unlocked…</p> <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>sched_ext: Fix this_rq() assumptions in dispatch kfuncs</p> <p>Under core scheduling, dispatch runs from within the core-wide pick and can target a sibling rq, so ops.dispatch() may execute on a CPU different from the dispatched rq&#39;s. Several kfunc paths assumed the two always coincide:</p> <p>- scx_dsq_move() decided whether an rq lock is held by testing this_rq()&#39;s rq flags and lock-danced accordingly. A dispatch for a sibling took the unlocked-context branch and acquired the source rq lock on top of the already held dispatched rq lock which could deadlock.</p> <p>- scx_bpf_sub_dispatch() dispatched this_rq() with its stashed sub_dispatch_prev, which is NULL when dispatching for a sibling.</p> <p>- finish_dispatch(), scx_bpf_dsq_reenq() and scx_bpf_dsq_nr_queued() resolved SCX_DSQ_LOCAL to this CPU&#39;s local DSQ rather than the dispatched rq&#39;s. The latter two are callable from other rq-locked operations too, where SCX_DSQ_LOCAL now likewise resolves to the op&#39;s rq. This changes behavior also without core scheduling, e.g. for ops.enqueue() running a remote wakeup on the waking CPU, and is intended: which CPU happens to execute an operation is incidental, the op&#39;s rq is what it is operating on, and the resolution now matches the insert side where SCX_DSQ_LOCAL dispatches land on the task&#39;s rq.</p> <p>Use the rq tracked by scx_locked_rq(), which is set to the dispatched rq around ops invocations and NULL in unlocked…</p> https://vulnerability.circl.lu/vuln/cve-2026-89518