CVE-2026-99085

sched_ext: Fix CPU hotplug hang when a dying CPU's tasks sit in the BPF scheduler

Description

In the Linux kernel, the following vulnerability has been resolved: sched_ext: Fix CPU hotplug hang when a dying CPU's tasks sit in the BPF scheduler A CPU going down has to empty its own rq. Its hotplug thread waits in sched_cpu_wait_empty() until nothing else is left, and the only thing that wakes it is balance_push(), which runs from __schedule() on the dying CPU and pushes off the migratable tasks the CPU picks. sched_ext breaks this. A task sitting on a user DSQ or held by the BPF scheduler is still counted on its rq, but an inactive CPU no longer calls ops.dispatch() and can't pull the task back. The dying CPU goes idle with the task still counted, and one of two things happens: - Another CPU consumes the task. The rq empties without a __schedule() on the dying CPU, so the hotplug thread is never woken and cpu_down() hangs holding cpu_hotplug_lock. - The task is affine only to the dying CPU. Nothing can move it, and the offline stalls until the watchdog ejects the BPF scheduler. When the rq goes offline, re-enqueue every task on it that isn't already on the local DSQ. An enqueue on an offline rq lands on the local DSQ, so the dying CPU itself picks the tasks and balance_push() pushes them off, the same as for the other sched classes. From then on no sched_ext path on another CPU can pull a task off the rq. ops.dispatch() currently stops as soon as the CPU goes inactive, and CPU hotplug then waits for an RCU grace period before taking the rq offline. A BPF-held task affine only to the dying CPU and preempted inside an RCU read-side critical section would block that grace period, and the rq would never go offline. Test SCX_RQ_ONLINE directly so that ops.dispatch() keeps running until the rq goes offline. Only the dying CPU's own hotplug thread clears the flag during teardown, and task_can_run_on_remote_rq() still keeps other rqs' tasks off the CPU.

Key facts

Published
23 Oct 2026
Last changed
23 Oct 2026
Assigned by
Linux
EPSS
0.164% likely to be exploited in the next 30 days, higher than 5.632% of CVEs (scores for 17 Nov 2026)

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

No explicit remediation statement is available on this page yet. Consult the original record and vendor references before choosing a fix.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
LinuxLinux
  • Default status: unaffected
  • f0e1a0643a59bf1f922fa209cec86a170b784f3f up to but excluding f79cd7a2df3768323fbfb9b0f96adff08fb7eb4c (affected)
  • f0e1a0643a59bf1f922fa209cec86a170b784f3f up to but excluding 638ee6bca19750934ea13f9c325f46fd8ae60064 (affected)
  • f0e1a0643a59bf1f922fa209cec86a170b784f3f up to but excluding 173ff9d03ec6373c3158b6e630af33a9b36fd216 (affected)
  • f0e1a0643a59bf1f922fa209cec86a170b784f3f up to but excluding d35a535d3e3e71f92a051d94e415f43612c4edfc (affected)
LinuxLinux
  • Default status: affected
  • 6.12 (affected)
  • 0 up to but excluding 6.12 (unaffected)
  • 6.12.114 up to and including 6.12.* (unaffected)
  • 6.18.58 up to and including 6.18.* (unaffected)
  • 7.2.12 up to and including 7.2.* (unaffected)
  • 7.3 up to and including * (unaffected)

Timeline

  1. 23 Oct 2026 Published

References