GPU VulnDB

Database/Kernel, userspace & hypervisor

Linux kernel sched_ext: a failed sub-scheduler enable races root disable into a use-after-free

CVE-2026-74731Kernel, userspace & hypervisorcurated

Impact

A sub-scheduler enable can fail before scx_link_sched() puts it in the hierarchy, yet cleanup still runs the full scx_sub_disable() path. An unlinked sub is invisible to drain_descendants(), which is the only ordering against root disable, so root teardown can exit every task to no scheduler between the sub's drain and its task walk; the walk then trips the membership WARN and re-homes exited tasks onto the dying hierarchy - a use-after-free. This only affects fleets that run BPF schedulers, which some operators do adopt on GPU nodes to tune data-loader and rank latency; on those, the failure mode is a kernel-side crash of the node's scheduling.

Who can reach it

Local root or CAP_SYS_ADMIN able to attach sched_ext schedulers, and specifically to a hierarchy with sub-schedulers where an enable fails while the root is being disabled. Not reachable by tenant workloads. Nodes with no scx scheduler loaded have no exposure.

What to do

Update to a stable kernel with the fix and reboot the node. Until then, the cheap interim is to avoid nested sub-scheduler hierarchies and to not tear down the root scheduler while sub-scheduler enables are in flight; unloading scx entirely removes the path if the latency tuning can wait.

References

Related entries

All Kernel, userspace & hypervisor entries

This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.