CVE-2026-99104 (GCVE-0-2026-99104)

Vulnerability from cvelistv5 – Published: 2026-10-28 10:34 – Updated: 2026-10-28 10:34
VLAI
Title
sched_ext: Fix the bypass dispatch claim for schedulers bypassed by an ancestor
Summary
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.
Severity
No CVSS data available.
Assigner
Linux CNA under the mitre root
CNA scorecard D 53/100 over 6637 records in the last 180 days details
References
Impacted products
Vendor Product Version CPE status
Linux Linux Affected: aa2a0a19686c90106ade6a7e848ffbb62d55d733 , < f0f18075e45d47bef7ff2eb9512ee4f0c7e5f9c7 (git)
Affected: aa2a0a19686c90106ade6a7e848ffbb62d55d733 , < 5bdeca322a6f8d10acaf67cccab1f69747ee7be3 (git)
guessed Create a notification for this product.
Linux Linux Affected: 7.1
Unaffected: 0 , < 7.1 (semver)
Unaffected: 7.2.13 , ≤ 7.2.* (semver)
Unaffected: 7.3 , ≤ * (original_commit_for_fix)
guessed Create a notification for this product.
Show details on NVD website
To clipboard 

{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "kernel/sched/ext/ext.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "f0f18075e45d47bef7ff2eb9512ee4f0c7e5f9c7",
              "status": "affected",
              "version": "aa2a0a19686c90106ade6a7e848ffbb62d55d733",
              "versionType": "git"
            },
            {
              "lessThan": "5bdeca322a6f8d10acaf67cccab1f69747ee7be3",
              "status": "affected",
              "version": "aa2a0a19686c90106ade6a7e848ffbb62d55d733",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "kernel/sched/ext/ext.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "7.1"
            },
            {
              "lessThan": "7.1",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "7.2.*",
              "status": "unaffected",
              "version": "7.2.13",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "7.3",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.2.13",
                  "versionStartIncluding": "7.1",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.3",
                  "versionStartIncluding": "7.1",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nsched_ext: Fix the bypass dispatch claim for schedulers bypassed by an ancestor\n\nscx_bypass() claims bypass dispatch when the scheduler\u0027s depth goes from\nzero to one and releases it when the depth returns to zero, but propagates\nonly the depth to the descendants, not the claim. A descendant that starts\nbypassing with its ancestor never claims, and one whose own bypass ends\nunder the ancestor\u0027s keeps its claim, as its depth does not return to zero.\n\nA sub-scheduler enable whose bypass ends under a PM suspend thus leaks its\nclaim: the parent keeps hosting bypass dispatch and the sub-scheduler\u0027s next\nbypass trips the WARN_ON_ONCE() on the claim. A sub-scheduler disable that\nstarts under a PM suspend has no claim, so once the resume lifts the root\u0027s\nbypass its tasks sit on the parent\u0027s bypass DSQs with nobody consuming them.\n\nClaim for every descendant whose depth goes from zero to one in the\npropagation and release every scheduler in the subtree whose depth returned\nto zero once the tasks have moved out of the bypass DSQs. A parent that is\nbypassing itself when a descendant claims consumes only its own bypass DSQs,\nempty until it leaves bypass and becomes the host."
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-10-28T10:34:23.729Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/f0f18075e45d47bef7ff2eb9512ee4f0c7e5f9c7"
        },
        {
          "url": "https://git.kernel.org/stable/c/5bdeca322a6f8d10acaf67cccab1f69747ee7be3"
        }
      ],
      "title": "sched_ext: Fix the bypass dispatch claim for schedulers bypassed by an ancestor",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2026-99104",
    "datePublished": "2026-10-28T10:34:23.729Z",
    "dateReserved": "2026-09-25T10:25:14.391Z",
    "dateUpdated": "2026-10-28T10:34:23.729Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2",
  "vulnerability-lookup:meta": {
    "epss": {
      "cve": "CVE-2026-99104",
      "date": "2026-11-05",
      "epss": "0.00173",
      "percentile": "0.06774"
    },
    "nvd": {
      "cve": {
        "affected": [
          {
            "affectedData": [
              {
                "defaultStatus": "unaffected",
                "product": "Linux",
                "programFiles": [
                  "kernel/sched/ext/ext.c"
                ],
                "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
                "vendor": "Linux",
                "versions": [
                  {
                    "lessThan": "f0f18075e45d47bef7ff2eb9512ee4f0c7e5f9c7",
                    "status": "affected",
                    "version": "aa2a0a19686c90106ade6a7e848ffbb62d55d733",
                    "versionType": "git"
                  },
                  {
                    "lessThan": "5bdeca322a6f8d10acaf67cccab1f69747ee7be3",
                    "status": "affected",
                    "version": "aa2a0a19686c90106ade6a7e848ffbb62d55d733",
                    "versionType": "git"
                  }
                ]
              },
              {
                "defaultStatus": "affected",
                "product": "Linux",
                "programFiles": [
                  "kernel/sched/ext/ext.c"
                ],
                "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
                "vendor": "Linux",
                "versions": [
                  {
                    "status": "affected",
                    "version": "7.1"
                  },
                  {
                    "lessThan": "7.1",
                    "status": "unaffected",
                    "version": "0",
                    "versionType": "semver"
                  },
                  {
                    "lessThanOrEqual": "7.2.*",
                    "status": "unaffected",
                    "version": "7.2.13",
                    "versionType": "semver"
                  },
                  {
                    "lessThanOrEqual": "*",
                    "status": "unaffected",
                    "version": "7.3",
                    "versionType": "original_commit_for_fix"
                  }
                ]
              }
            ],
            "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
          }
        ],
        "cveTags": [],
        "descriptions": [
          {
            "lang": "en",
            "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nsched_ext: Fix the bypass dispatch claim for schedulers bypassed by an ancestor\n\nscx_bypass() claims bypass dispatch when the scheduler\u0027s depth goes from\nzero to one and releases it when the depth returns to zero, but propagates\nonly the depth to the descendants, not the claim. A descendant that starts\nbypassing with its ancestor never claims, and one whose own bypass ends\nunder the ancestor\u0027s keeps its claim, as its depth does not return to zero.\n\nA sub-scheduler enable whose bypass ends under a PM suspend thus leaks its\nclaim: the parent keeps hosting bypass dispatch and the sub-scheduler\u0027s next\nbypass trips the WARN_ON_ONCE() on the claim. A sub-scheduler disable that\nstarts under a PM suspend has no claim, so once the resume lifts the root\u0027s\nbypass its tasks sit on the parent\u0027s bypass DSQs with nobody consuming them.\n\nClaim for every descendant whose depth goes from zero to one in the\npropagation and release every scheduler in the subtree whose depth returned\nto zero once the tasks have moved out of the bypass DSQs. A parent that is\nbypassing itself when a descendant claims consumes only its own bypass DSQs,\nempty until it leaves bypass and becomes the host."
          }
        ],
        "id": "CVE-2026-99104",
        "lastModified": "2026-10-28T11:17:29.733",
        "metrics": {},
        "published": "2026-10-28T11:17:29.733",
        "references": [
          {
            "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
            "url": "https://git.kernel.org/stable/c/5bdeca322a6f8d10acaf67cccab1f69747ee7be3"
          },
          {
            "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
            "url": "https://git.kernel.org/stable/c/f0f18075e45d47bef7ff2eb9512ee4f0c7e5f9c7"
          }
        ],
        "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "vulnStatus": "Received"
      }
    },
    "redhat_vex": {
      "aggregate_severity": "Moderate",
      "current_release_date": "2026-11-06T03:25:26+00:00",
      "cve": "CVE-2026-99104",
      "id": "CVE-2026-99104",
      "initial_release_date": "2026-10-28T00:00:00+00:00",
      "product_status:known_not_affected": "203",
      "source": "Red Hat CSAF VEX",
      "status": "final",
      "title": "kernel: sched_ext: Fix the bypass dispatch claim for schedulers bypassed by an ancestor",
      "url": "https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-99104.json",
      "version": "3"
    },
    "suse_vex": {
      "aggregate_severity": "low",
      "current_release_date": "2026-11-04T16:00:54Z",
      "cve": "CVE-2026-99104",
      "id": "CVE-2026-99104",
      "initial_release_date": "2026-10-28T17:35:05Z",
      "product_status:known_not_affected": "348",
      "source": "SUSE CSAF VEX",
      "status": "interim",
      "title": "SUSE CVE CVE-2026-99104",
      "url": "https://ftp.suse.com/pub/projects/security/csaf-vex/2026/cve-2026-99104.json",
      "version": "4"
    }
  }
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

JSON
How durations are calculated

Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.

Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.

Loading timeline…




    Related by attack behaviour

    Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.