CVE-2026-99524: sched_ext: Fix use-after-free of a local reenq node left on an inactive cpu
In the Linux kernel, the following vulnerability has been resolved:
schedext: Fix use-after-free of a local reenq node left on an inactive cpu
A local DSQ reenq is queued on the rq through a per-sched node and run from deferred work. When the reenq is requested from dispatch, the work is a balance callback queued once dispatch is done. A cpu going down installs balance push early in its teardown, and queuebalancecallback() refuses new callbacks from then on. ops.dispatch() keeps running on that cpu until the rq goes offline after an RCU grace period, so a reenq it requests in that window may never run. The IMMED handling in dispatchone() requests one the same way.
A reenq requested from elsewhere for a cpu that is already offline goes through irqworkqueueon(), which warns, and its work doesn't run until the cpu comes back.
Either way the node stays on the rq's list. When the scheduler is freed, scxschedfreercuwork() warns and frees the pcpu with the node still linked, and the list is walked again once the cpu comes back.
An inactive cpu's local DSQ holds only tasks that are bound to it or are being moved off, so the reenq is pointless. Ignore reenqs of an inactive cpu's local DSQ.
The test is lockless. The hotplug thread of a cpu going down runs on that cpu, and it marks the cpu inactive before it installs balance push. A dispatch on the cpu runs to completion before that thread can run there, so a dispatch that saw the cpu active has queued its callback by then. Requests from outside dispatch run from the wakeup path or through irqwork, which balance push doesn't affect. The grace period after the cpu goes inactive waits for any requester that saw it active, so that irqwork is queued while the cpu is online.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 7.3.2 - Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 7.3.3-1 - Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 6.1.176-1Fixed in 6.1.192-2Fixed in 6.12.107-1Fixed in 6.12.117-1Fixed in 7.3.4-1Fixed in 7.3.5-1