Skip to content
Threat Brief

← All advisories

CVE-2026-99085

Severity unknownNo known exploitationFix available

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

Record last updated

CVSS score

None

No score published yet

EPSS, chance of exploitation in 30 days

0.2%

Higher than 6% of scored CVEs. A prediction, not evidence.

CISA remediation deadline

None

Not in the KEV catalog

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.

Patching and mitigation

Patch status
Fix available (source: Microsoft MSRC)
Fix documented (source date)
Mitigation
None documented
Vendor guidance
msrc.microsoft.com (opens in a new tab)

Affected products

VendorProductAffected versionsFixed inPer
LinuxLinuxfrom f0e1a0643a59bf1f922fa209cec86a170b784f3f before f79cd7a2df3768323fbfb9b0f96adff08fb7eb4cf79cd7a2df3768323fbfb9b0f96adff08fb7eb4cCVE Program
LinuxLinuxfrom f0e1a0643a59bf1f922fa209cec86a170b784f3f before 638ee6bca19750934ea13f9c325f46fd8ae60064638ee6bca19750934ea13f9c325f46fd8ae60064CVE Program
LinuxLinuxfrom f0e1a0643a59bf1f922fa209cec86a170b784f3f before 173ff9d03ec6373c3158b6e630af33a9b36fd216173ff9d03ec6373c3158b6e630af33a9b36fd216CVE Program
LinuxLinuxfrom f0e1a0643a59bf1f922fa209cec86a170b784f3f before d35a535d3e3e71f92a051d94e415f43612c4edfcd35a535d3e3e71f92a051d94e415f43612c4edfcCVE Program
LinuxLinux6.12Not documentedCVE Program
Microsoftazl4 kernel 6.18.57-1.12.azl4 on Azure Linux 4.0Not documented0:6.18.62-1.1.azl4Microsoft MSRC
LinuxLinux (unaffected)from 6.12.114 up to and including 6.12.*Not documentedCVE Program
LinuxLinux (unaffected)from 6.18.58 up to and including 6.18.*Not documentedCVE Program
LinuxLinux (unaffected)from 7.2.12 up to and including 7.2.*Not documentedCVE Program
LinuxLinux (unaffected)7.3Not documentedCVE Program
LinuxLinux (unaffected)all versions before 6.12Not documentedCVE Program

Timeline

  1. Disclosure

    CVE record published by Linux

    Source: CVE Program (opens in a new tab)

  2. Advisory

    Microsoft advisory published

    Source: Microsoft MSRC (opens in a new tab)

  3. Advisory change

    Microsoft advisory revised (2.0): Information published.

    Source: Microsoft MSRC (opens in a new tab)

  4. Patch

    Fix documented by Microsoft MSRC

    Source: Microsoft MSRC (opens in a new tab)

Vendor guidance and references