sched_ext: Wait for SCX_OPSS_DISPATCHING before reenqueueing a task
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 43457bf6550044c40bd6d3fcdf9ea66f5a55d139 and Kernel 7de9a6fb44eae4f05e68c805d58b9c618815adfa.
In the Linux kernel, the following vulnerability has been resolved: sched_ext: Wait for SCX_OPSS_DISPATCHING before reenqueueing a task ebf1ccff79c4 ("sched_ext: Fix ops.dequeue() semantics") moved the final ops_state store in scx_dispatch_enqueue() after the DSQ unlock so that the custody update and ops.dequeue() precede it. A task can thus be found on a DSQ while still SCX_OPSS_DISPATCHING. The dequeue and core-sched pick paths wait for the state to clear in ops_dequeue() but the reenqueue paths don't. A reenqueue in that window runs ops.enqueue() and sets SCX_OPSS_QUEUED before the dispatch has completed. The dispatcher's final store then overwrites it with SCX_OPSS_NONE and finish_dispatch() drops every later dispatch of the task. Wait for SCX_OPSS_DISPATCHING to clear before dequeueing a task for reenqueue, the same way ops_dequeue() does.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =7.1, >=ebf1ccff79c43f860cbd2f9d6cfab9a462d0cb2d <43457bf6550044c40bd6d3fcdf9ea66f5a55d139, >=ebf1ccff79c43f860cbd2f9d6cfab9a462d0cb2d <7de9a6fb44eae4f05e68c805d58b9c618815adfa | 43457bf6550044c40bd6d3fcdf9ea66f5a55d139, 7de9a6fb44eae4f05e68c805d58b9c618815adfa |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket