CVE-2026-99595

published 20 Nov 2026 · updated 20 Nov 2026

sched/fair: Clear throttle state when leaving the fair class

5.0MediumEPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel b91da5a7f8bc9ff522c5554c1a1934c2cb7991fe, Kernel c282051fc2cae2ea54770ebe435dbea090272c25 and Kernel 7.3.5.

In the Linux kernel, the following vulnerability has been resolved: sched/fair: Clear throttle state when leaving the fair class Task-based CFS bandwidth throttling removes a task's fair sched_entity while the scheduler core still considers the task queued. p->throttled carries the fair-specific state across dequeue/enqueue operations. DEQUEUE_CLASS removes the task from cfs_rq->throttled_limbo_list but retains the bit. If the last finite CFS quota is disabled while the task runs in another class, it is absent from the unthrottle walk and the bit survives. Returning to fair while cfs_bandwidth_used() is false then performs a real fair enqueue with p->throttled still set. After bandwidth is re-enabled, a class-change dequeue treats the stale bit as limbo state and skips __dequeue_task(). p->se.on_rq therefore remains set, and put_prev_task_fair() places the entity in the EEVDF tree while the task moves to RT. On exit, the fair picker can select the TASK_DEAD task. __schedule() then returns to do_task_dead(), which hits BUG(). Keep p->throttled across migrations and group moves, but clear it on DEQUEUE_CLASS because fair-specific state must not outlive fair-class membership. A later return to fair uses the normal enqueue path. That path still respects a throttled cfs_rq. A KASAN, LOCKDEP and DEBUG_LIST v7.3 kernel reproduced the do_task_dead() BUG in 3/3 root and 3/3 delegated uid-1000 runs with CapPrm=CapEff=0 and RLIMIT_RTPRIO=1. The fix passed both matrices plus a 3/3 class-switch control with bandwidth continuously enabled, without a scheduler warning, KASAN report, lockdep splat or crash. An AI coding assistant analyzed the state mismatch and drafted the initial reproducer, fix candidate and this changelog. The source paths, trigger, controls and results were rechecked against the cited revisions.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel=6.18, >=e1fad12dcb66b7f35573c52b665830a1538f9886 <b91da5a7f8bc9ff522c5554c1a1934c2cb7991fe, >=e1fad12dcb66b7f35573c52b665830a1538f9886 <c282051fc2cae2ea54770ebe435dbea090272c25b91da5a7f8bc9ff522c5554c1a1934c2cb7991fe, c282051fc2cae2ea54770ebe435dbea090272c25
linux-kernel: Kernel>=6.18.0 <7.3.57.3.5

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-99595 severity on Zeptric[![CVE-2026-99595](https://zeptric.io/badge/cve/CVE-2026-99595.svg)](https://zeptric.io/cve/CVE-2026-99595)