Skip to main content
VulnerabilityPublished

CVE-2026-99595: Linux kernel · sched/fair: Clear throttle state when leaving the fair class

Affects Linux kernelSource CVE Database V5

0
Compare

Not known to be exploited : upgrade to c282051fc2cae2ea54770ebe435dbea090272c25 or b91da5a7f8bc9ff522c5554c1a1934c2cb7991fe when convenient.

Data as of 20 Nov 2026, 06:19 UTC

Severity
Unrated

Rated by Threat Radar · CVSS not yet scored by NVD

Thin evidence

One scorer or none
Patch
Available – fixed in c282051fc2cae2ea54770ebe435dbea090272c25, b91da5a7f8bc9ff522c5554c1a1934c2cb7991fe

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 19 Nov 2026.

What to do

Upgrade Linux kernel to c282051fc2cae2ea54770ebe435dbea090272c25 or b91da5a7f8bc9ff522c5554c1a1934c2cb7991fe.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ e1fad12dcb66b7f35573c52b665830a1538f9886, < c282051fc2cae2ea54770ebe435dbea090272c25
Fixed in
  • c282051fc2cae2ea54770ebe435dbea090272c25
LinuxLinuxAffected
  • ≥ e1fad12dcb66b7f35573c52b665830a1538f9886, < b91da5a7f8bc9ff522c5554c1a1934c2cb7991fe
Fixed in
  • b91da5a7f8bc9ff522c5554c1a1934c2cb7991fe
LinuxLinuxAffected
  • =6.18
Fixed in–

Description

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.

References

Community reviews

Loading reviews…