GPU VulnDB

Database/Kernel, userspace & hypervisor

Linux kernel sched/core: core-scheduling selection corrupted by lock-dropping picks and concurrent flips

UnscoredCVE-2026-89520Kernel, userspace & hypervisor+1 more CVEscurated

Impact

The core-scheduling side of the same problem, in generic sched/core rather than in sched_ext. A ->pick_task() that releases the rq lock leaves every sibling __lock momentarily free, so __sched_core_flip(false) can complete mid-selection and rebind rq_lockp() underneath it: the selection then touches sibling state it no longer protects, and __schedule() releases a lock it never took while leaking the one it did. Separately, the single-CPU fast path can commit an uncookied pick even though the core went cookied during the release, and forceidle accounting is skewed by an interleaving pass. The fixes count in-flight selections in the leader's rq->core_pick_in_flight so flips wait for them to drain, and restart the whole selection when a pick returns RETRY_TASK. The vendor split this across two ids (CVE-2026-89521); one flaw, one remediation. Consequence on a GPU node is rq-lock imbalance and hard hangs - every job on the node goes with it.

Who can reach it

Local, on nodes with core scheduling enabled together with a scheduling class whose pick can drop the rq lock (in practice sched_ext). Enabling core scheduling and loading the scheduler takes root; after that, cookie lifetime events and normal scheduling hit the race.

What to do

Take the stable kernel update carrying both changes - the flip waits for in-flight core-wide selections, and the selection restarts above its state derivation on RETRY_TASK - and reboot each node. Interim option: disable core scheduling on affected nodes, or run without a lock-dropping scheduling class. The record gives commits only, no fixed release numbers.

Also covers 1 CVE

The vendor assigned a separate id to each affected code path. They share this advisory, this score and this fix, so they are one entry here.

CVE-2026-89521

References

Related entries

All Kernel, userspace & hypervisor entries

This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.