CVE-2026-99104

sched_ext: Fix the bypass dispatch claim for schedulers bypassed by an ancestor

Published Oct 28, 2026 CVSS 3.1 · 4.1 Medium EPSS < 1% KEV · Not listed
Description
In the Linux kernel, the following vulnerability has been resolved:

sched_ext: Fix the bypass dispatch claim for schedulers bypassed by an ancestor

scx_bypass() claims bypass dispatch when the scheduler's depth goes from
zero to one and releases it when the depth returns to zero, but propagates
only the depth to the descendants, not the claim. A descendant that starts
bypassing with its ancestor never claims, and one whose own bypass ends
under the ancestor's keeps its claim, as its depth does not return to zero.

A sub-scheduler enable whose bypass ends under a PM suspend thus leaks its
claim: the parent keeps hosting bypass dispatch and the sub-scheduler's next
bypass trips the WARN_ON_ONCE() on the claim. A sub-scheduler disable that
starts under a PM suspend has no claim, so once the resume lifts the root's
bypass its tasks sit on the parent's bypass DSQs with nobody consuming them.

Claim for every descendant whose depth goes from zero to one in the
propagation and release every scheduler in the subtree whose depth returned
to zero once the tasks have moved out of the bypass DSQs. A parent that is
bypassing itself when a descendant claims consumes only its own bypass DSQs,
empty until it leaves bypass and becomes the host.

Analysis

AI-generated

Technical impact

The Linux kernel scheduler contains an error in propagating bypass claims. When a scheduler’s depth changes from zero to one, the claim is not passed to descendant schedulers, leading to stale or missing claims. During power‑management transitions a sub‑scheduler may inherit an incorrect claim or lose its claim, causing tasks to remain on depth‑synchronization queues that are never consumed. This can stall work and potentially freeze the system, resulting in a service interruption.

Affected Systems

All Linux kernel releases are potentially affected because the patch modifies core scheduler code. No specific kernel version range is listed, so any kernel version before the commit that introduced the fix may be vulnerable. The flaw applies to all Linux operating systems that use the Linux kernel.

Risk and Exploitability

The CVSS score of 4.1 indicates a low to moderate severity, and the EPSS score is below 1%, suggesting that public exploitation is unlikely. The flaw is not listed in the CISA KEV catalog, and no public exploits are known. The most likely attack vector is an internal kernel event such as a power‑management transition; this is inferred because the description does not explicitly state the required access level. The vulnerability requires specific kernel conditions and is not externally exploitable through the network, so the chance of successful exploitation is low, but if triggered the impact could be a denial of service.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Apply the kernel patch from commit 5bdeca322a6f8d10acaf67cccab1f69747ee7be3 or commit f0f18075e45d47bef7ff2eb9512ee4f0c7e5f9c7.
  • Reboot the system so the updated kernel loads and the scheduler bypass claims are correctly handled.
  • Monitor kernel logs for WARN_ON_ONCE messages related to scheduler bypass claims and ensure no scheduling stalls occur after resume.

Generated by OpenCVE AI on October 29, 2026 at 20:13 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Weaknesses CWE-665
Type Values Removed Values Added
Weaknesses CWE-911
References
Metrics threat_severity

None

cvssV3_1

{'score': 4.1, 'vector': 'CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:H'}

threat_severity

Moderate

Type Values Removed Values Added
Weaknesses CWE-665
Type Values Removed Values Added
First Time appeared Linux linux
Vendors & Products Linux linux
Type Values Removed Values Added
Description In the Linux kernel, the following vulnerability has been resolved: sched_ext: Fix the bypass dispatch claim for schedulers bypassed by an ancestor scx_bypass() claims bypass dispatch when the scheduler's depth goes from zero to one and releases it when the depth returns to zero, but propagates only the depth to the descendants, not the claim. A descendant that starts bypassing with its ancestor never claims, and one whose own bypass ends under the ancestor's keeps its claim, as its depth does not return to zero. A sub-scheduler enable whose bypass ends under a PM suspend thus leaks its claim: the parent keeps hosting bypass dispatch and the sub-scheduler's next bypass trips the WARN_ON_ONCE() on the claim. A sub-scheduler disable that starts under a PM suspend has no claim, so once the resume lifts the root's bypass its tasks sit on the parent's bypass DSQs with nobody consuming them. Claim for every descendant whose depth goes from zero to one in the propagation and release every scheduler in the subtree whose depth returned to zero once the tasks have moved out of the bypass DSQs. A parent that is bypassing itself when a descendant claims consumes only its own bypass DSQs, empty until it leaves bypass and becomes the host.
Title sched_ext: Fix the bypass dispatch claim for schedulers bypassed by an ancestor
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References
Weaknesses
  • CWE-911

    Improper Update of Reference Count

Sources

Status
PUBLISHED
Assigner
Linux
Published
Updated
Oct 28, 2026, 10:34 AM
Reserved
Sep 25, 2026, 10:25 AM
Status
Received
Published
Oct 28, 2026, 11:17 AM
Modified
Oct 28, 2026, 11:17 AM
Severity
Moderate
Public date
Oct 28, 2026, 12:00 AM