PT-2026-152475
CVE-2026-99595
·
Published
2026-11-20
·
Updated
2026-11-20
Description by
Score
N/A
Not availableNo severity ratings or metrics are available. When they are, we'll update the corresponding info on the page.
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.
Found an issue in the description? Have something to add? Feel free to write us 👾