CVE-2026-89517 (GCVE-0-2026-89517)

Vulnerability from cvelistv5 – Published: 2026-09-11 19:44 – Updated: 2026-10-19 08:48
VLAI
Title
sched_ext: Fix rq->core_pick corruption under core scheduling
Summary
In the Linux kernel, the following vulnerability has been resolved: sched_ext: Fix rq->core_pick corruption under core scheduling Core scheduling's pick_next_task() picks what to run on every SMT sibling of the core in a single pass under the shared core-wide rq lock. The selection state is consistent only while the lock is held continuously, so ->pick_task() originally could not release it. However, since 4c95380701f5 ("sched/ext: Fold balance_scx() into pick_task_scx()"), sched_ext runs dispatch from inside the pick and dispatching can drop the rq lock. To support this, pick_next_task() has been updated to restart the whole selection when a pick returns RETRY_TASK after releasing the lock. When selections on the same core interleave through the dropped lock, they corrupt each other's state: one clears the other's rq->core_pick leading to a NULL deref, or invalidates its keep-the-previous-task decision leaving a dequeued task running, which deadlocks the next wakeup and matches the reported hard hangs. A cookied ping-pong load on an SMT machine makes the interleavings frequent and kills the kernel within seconds. Fix it by making the pick return RETRY_TASK whenever dispatch released the rq lock, so that a selection only ever commits picks made under a continuously held lock. The previous patch's rq->scx.lock_drop_seq counts the releases. A dispatch that touched nothing never releases the lock and its verdict, including "nothing to run", stands: retries are bounded, each following a dispatch that actually did something, and an idle CPU does not loop. If another dispatch is already in flight on the rq, skip dispatching and pick from what is already queued locally - the in-flight dispatch has released the lock, so its own selection will retry and re-pick this rq, while returning RETRY_TASK here would only spin on the lock that dispatch needs to finish. Balance callbacks must run in the context that queued them, so they can only be queued on the CPU's own rq. When dispatching for another rq, run the deferred work directly instead - that rq may consume all its picks through the core-sched fast path and never queue the callback itself. The put_prev_task_scx() warning about a runnable task being left behind assumed that dispatch ran as part of the very pick that is switching away. That now only holds on the non-core path, so gate it and drop the cookie-match test, which is always true without core scheduling, from its condition.
Severity
No CVSS data available.
Assigner
Linux CNA under the mitre root
CNA scorecard D 53/100 over 6643 records in the last 180 days details
References
Impacted products
Vendor Product Version CPE status
Linux Linux Affected: 4c95380701f58b8112f0b891de8d160e4199e19d , < cdafb68155bee2d5c4e50c12e4606323e9334e6b (git)
Affected: 4c95380701f58b8112f0b891de8d160e4199e19d , < d954004205c1a1d3f59ce8482b559266c15600fa (git)
guessed Create a notification for this product.
Linux Linux Affected: 6.19
Unaffected: 0 , < 6.19 (semver)
Unaffected: 7.2.4 , ≤ 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": "cdafb68155bee2d5c4e50c12e4606323e9334e6b",
              "status": "affected",
              "version": "4c95380701f58b8112f0b891de8d160e4199e19d",
              "versionType": "git"
            },
            {
              "lessThan": "d954004205c1a1d3f59ce8482b559266c15600fa",
              "status": "affected",
              "version": "4c95380701f58b8112f0b891de8d160e4199e19d",
              "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": "6.19"
            },
            {
              "lessThan": "6.19",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "7.2.*",
              "status": "unaffected",
              "version": "7.2.4",
              "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.4",
                  "versionStartIncluding": "6.19",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.3",
                  "versionStartIncluding": "6.19",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nsched_ext: Fix rq-\u003ecore_pick corruption under core scheduling\n\nCore scheduling\u0027s pick_next_task() picks what to run on every SMT sibling of\nthe core in a single pass under the shared core-wide rq lock. The selection\nstate is consistent only while the lock is held continuously, so\n-\u003epick_task() originally could not release it. However, since 4c95380701f5\n(\"sched/ext: Fold balance_scx() into pick_task_scx()\"), sched_ext runs\ndispatch from inside the pick and dispatching can drop the rq lock. To\nsupport this, pick_next_task() has been updated to restart the whole\nselection when a pick returns RETRY_TASK after releasing the lock.\n\nWhen selections on the same core interleave through the dropped lock, they\ncorrupt each other\u0027s state: one clears the other\u0027s rq-\u003ecore_pick leading to\na NULL deref, or invalidates its keep-the-previous-task decision leaving a\ndequeued task running, which deadlocks the next wakeup and matches the\nreported hard hangs. A cookied ping-pong load on an SMT machine makes the\ninterleavings frequent and kills the kernel within seconds.\n\nFix it by making the pick return RETRY_TASK whenever dispatch released the\nrq lock, so that a selection only ever commits picks made under a\ncontinuously held lock. The previous patch\u0027s rq-\u003escx.lock_drop_seq counts\nthe releases. A dispatch that touched nothing never releases the lock and\nits verdict, including \"nothing to run\", stands: retries are bounded, each\nfollowing a dispatch that actually did something, and an idle CPU does not\nloop.\n\nIf another dispatch is already in flight on the rq, skip dispatching and\npick from what is already queued locally - the in-flight dispatch has\nreleased the lock, so its own selection will retry and re-pick this rq,\nwhile returning RETRY_TASK here would only spin on the lock that dispatch\nneeds to finish.\n\nBalance callbacks must run in the context that queued them, so they can only\nbe queued on the CPU\u0027s own rq. When dispatching for another rq, run the\ndeferred work directly instead - that rq may consume all its picks through\nthe core-sched fast path and never queue the callback itself.\n\nThe put_prev_task_scx() warning about a runnable task being left behind\nassumed that dispatch ran as part of the very pick that is switching away.\nThat now only holds on the non-core path, so gate it and drop the\ncookie-match test, which is always true without core scheduling, from its\ncondition."
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-10-19T08:48:08.592Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/cdafb68155bee2d5c4e50c12e4606323e9334e6b"
        },
        {
          "url": "https://git.kernel.org/stable/c/d954004205c1a1d3f59ce8482b559266c15600fa"
        }
      ],
      "title": "sched_ext: Fix rq-\u003ecore_pick corruption under core scheduling",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2026-89517",
    "datePublished": "2026-09-11T19:44:00.576Z",
    "dateReserved": "2026-09-11T19:38:34.717Z",
    "dateUpdated": "2026-10-19T08:48:08.592Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2",
  "vulnerability-lookup:meta": {
    "epss": {
      "cve": "CVE-2026-89517",
      "date": "2026-11-10",
      "epss": "0.00198",
      "percentile": "0.0959"
    },
    "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": "cdafb68155bee2d5c4e50c12e4606323e9334e6b",
                    "status": "affected",
                    "version": "4c95380701f58b8112f0b891de8d160e4199e19d",
                    "versionType": "git"
                  },
                  {
                    "lessThan": "d954004205c1a1d3f59ce8482b559266c15600fa",
                    "status": "affected",
                    "version": "4c95380701f58b8112f0b891de8d160e4199e19d",
                    "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": "6.19"
                  },
                  {
                    "lessThan": "6.19",
                    "status": "unaffected",
                    "version": "0",
                    "versionType": "semver"
                  },
                  {
                    "lessThanOrEqual": "7.2.*",
                    "status": "unaffected",
                    "version": "7.2.4",
                    "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 rq-\u003ecore_pick corruption under core scheduling\n\nCore scheduling\u0027s pick_next_task() picks what to run on every SMT sibling of\nthe core in a single pass under the shared core-wide rq lock. The selection\nstate is consistent only while the lock is held continuously, so\n-\u003epick_task() originally could not release it. However, since 4c95380701f5\n(\"sched/ext: Fold balance_scx() into pick_task_scx()\"), sched_ext runs\ndispatch from inside the pick and dispatching can drop the rq lock. To\nsupport this, pick_next_task() has been updated to restart the whole\nselection when a pick returns RETRY_TASK after releasing the lock.\n\nWhen selections on the same core interleave through the dropped lock, they\ncorrupt each other\u0027s state: one clears the other\u0027s rq-\u003ecore_pick leading to\na NULL deref, or invalidates its keep-the-previous-task decision leaving a\ndequeued task running, which deadlocks the next wakeup and matches the\nreported hard hangs. A cookied ping-pong load on an SMT machine makes the\ninterleavings frequent and kills the kernel within seconds.\n\nFix it by making the pick return RETRY_TASK whenever dispatch released the\nrq lock, so that a selection only ever commits picks made under a\ncontinuously held lock. The previous patch\u0027s rq-\u003escx.lock_drop_seq counts\nthe releases. A dispatch that touched nothing never releases the lock and\nits verdict, including \"nothing to run\", stands: retries are bounded, each\nfollowing a dispatch that actually did something, and an idle CPU does not\nloop.\n\nIf another dispatch is already in flight on the rq, skip dispatching and\npick from what is already queued locally - the in-flight dispatch has\nreleased the lock, so its own selection will retry and re-pick this rq,\nwhile returning RETRY_TASK here would only spin on the lock that dispatch\nneeds to finish.\n\nBalance callbacks must run in the context that queued them, so they can only\nbe queued on the CPU\u0027s own rq. When dispatching for another rq, run the\ndeferred work directly instead - that rq may consume all its picks through\nthe core-sched fast path and never queue the callback itself.\n\nThe put_prev_task_scx() warning about a runnable task being left behind\nassumed that dispatch ran as part of the very pick that is switching away.\nThat now only holds on the non-core path, so gate it and drop the\ncookie-match test, which is always true without core scheduling, from its\ncondition."
          }
        ],
        "id": "CVE-2026-89517",
        "lastModified": "2026-10-19T09:17:46.147",
        "metrics": {},
        "published": "2026-09-11T20:19:34.287",
        "references": [
          {
            "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
            "url": "https://git.kernel.org/stable/c/cdafb68155bee2d5c4e50c12e4606323e9334e6b"
          },
          {
            "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
            "url": "https://git.kernel.org/stable/c/d954004205c1a1d3f59ce8482b559266c15600fa"
          }
        ],
        "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "vulnStatus": "Received"
      }
    },
    "redhat_vex": {
      "aggregate_severity": "Moderate",
      "current_release_date": "2026-11-06T01:16:53+00:00",
      "cve": "CVE-2026-89517",
      "id": "CVE-2026-89517",
      "initial_release_date": "2026-09-11T00:00:00+00:00",
      "product_status:known_affected": "1",
      "product_status:known_not_affected": "202",
      "source": "Red Hat CSAF VEX",
      "status": "final",
      "title": "kernel: sched_ext: Fix rq-\u003ecore_pick corruption under core scheduling",
      "url": "https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-89517.json",
      "version": "3"
    }
  }
}



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.