Skip to content
Heist/ feed
Unrated

sched_ext: Keep kick_sync waiting on the rq's own CPU

Type: advisorySource: Official CVE List1 source record

In the Linux kernel, the following vulnerability has been resolved: sched_ext: Keep kick_sync waiting on the rq's own CPU kick_sync_wait_bal_cb() assumes it runs on the rq's CPU from the __schedule() tail: the snapshots it compares against live in that CPU's percpu area and the busy-wait runs with the rq lock dropped and IRQs enabled. However, dispatch can now drop the rq lock while the callback sits queued, and rq lock takers in that window (the sched class change paths, the scx task iterator) flush pending balance callbacks on release, running the callback on a foreign CPU. Such a run compares against unrelated snapshots and can deadlock when the executing CPU is itself a wait target. Bail on a foreign CPU and leave the wait state alone. The wait only observes progress that the resched kicks already guarantee and the rq's next wait picks up the stale cpus_to_sync bits.

Announced Source revision 1
Original source ↗

CVE-2026-93220

Primary source · Revision 1

Imported from structured advisory data. Source references identify upstream records or fields; verify affected versions and your deployed configuration.

Security context

Source reference: cve:CVE-2026-93220

Linux

Source reference: /containers/cna/affected/0/product

Affected versions
Not stated in this record
Fixed versions
Not stated in this record
Prerequisites
Not stated in this record

Linux

Source reference: /containers/cna/affected/1/product

Affected versions
Not stated in this record
Fixed versions
Not stated in this record
Prerequisites
Not stated in this record

Structured affected-version data

Original package identities and version rules from this source.

[
  {
    "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
    "vendor": "Linux",
    "product": "Linux",
    "versions": [
      {
        "status": "affected",
        "version": "4c95380701f58b8112f0b891de8d160e4199e19d",
        "lessThan": "c736ea0fe7b4df920da6bd43a81c5eeecadcc8be",
        "versionType": "git"
      },
      {
        "status": "affected",
        "version": "4c95380701f58b8112f0b891de8d160e4199e19d",
        "lessThan": "e0253dd04beb03e79477c5ef4768b11135687206",
        "versionType": "git"
      }
    ],
    "programFiles": [
      "kernel/sched/ext/ext.c"
    ],
    "defaultStatus": "unaffected"
  },
  {
    "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
    "vendor": "Linux",
    "product": "Linux",
    "versions": [
      {
        "status": "affected",
        "version": "6.19"
      },
      {
        "status": "unaffected",
        "version": "0",
        "lessThan": "6.19",
        "versionType": "semver"
      },
      {
        "status": "unaffected",
        "version": "7.2.4",
        "versionType": "semver",
        "lessThanOrEqual": "7.2.*"
      },
      {
        "status": "unaffected",
        "version": "7.3",
        "versionType": "original_commit_for_fix",
        "lessThanOrEqual": "*"
      }
    ],
    "programFiles": [
      "kernel/sched/ext/ext.c"
    ],
    "defaultStatus": "affected"
  }
]
Related CVEs
CVE-2026-93220

Source reference: /cveMetadata/cveId

Publisher severity

No explicit severity was provided.

Event
#37922 · Revision 1
Added to Heist Feed
Publisher date
Read the original announcement