Skip to main content

CVE-2026-99595Linux vulnerability

Low priorityNot scoredEPSS not scored yet

CVE-2026-99595 is a vulnerability in Linux, not yet scored.

Why this priority: Not scored yet, and no exploitation signal.

Published · Updated · NVD status: Received

What it is

The record does not classify the weakness yet; the description below says what the reporter found.

How it is reached

The record does not say yet how the flaw is reached; the description below is the best guide until it is scored.

What an attacker gains

Its impact has not been scored yet.

Is it being exploited?

There is no public report of exploitation yet.

What to do

  1. Upgrade Linux to a fixed version for your release line (7.3.5, 7.4-rc2).

Description from NVD

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.

What this means for your architecture.

A CVE names a product. Whether it matters depends on where that product sits in your systems: what reaches it, which trust boundary it guards and what it can reach once compromised. Veriom maps your components, their relationships and your trust boundaries from your code, cloud and delivery evidence, so you can see where a component like this sits. The radar itself does not look at your systems.

Components it touches

  • Linux. Start from where it runs and what it is connected to.

Trust boundaries in play

    Questions to answer about your own systems

    • Where does Linux run in your systems, and at which version?
    • Which of those instances are reachable by people you do not trust?
    • What can it reach once compromised: which data stores, secrets and services?

    14-day free trial

    Understand how your systems connect.

    See your services, dependencies and trust boundaries in one place, with evidence from your connected environment.

    Sources

    • CVE records and CVSS scores from the NVD CVE API. This product uses the NVD API but is not endorsed or certified by the NVD.
    • Exploitation status from CISA’s Known Exploited Vulnerabilities catalog.
    • Exploit likelihood from FIRST’s Exploit Prediction Scoring System (EPSS), refreshed daily.
    • Explanations are written by Veriom from fixed templates over each record’s data, not by a person reviewing each CVE. Descriptions are quoted from the records as published.