Answer in brief
CVE-2026-89520 records a Unknown severity vulnerability in sched/core: Make core-sched flips wait for in-flight selections. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=539f65125d20aacab54d02d77f10a839f45b09dc <9d69422ddaa13526c2223444e237d948d6e44728 || >=539f65125d20aacab54d02d77f10a839f45b09dc <23eda24f325a6e6d686d30ec75f2e9d6745e2015 || >=539f65125d20aacab54d02d77f10a839f45b09dc <f3629c63a4af3e491381780bc6c123cb498c4c40 | 9d69422ddaa13526c2223444e237d948d6e44728, 23eda24f325a6e6d686d30ec75f2e9d6745e2015, f3629c63a4af3e491381780bc6c123cb498c4c40 |
| Linux/Linuxgeneric | 5.14 | Not reported |
Published upstream
Sep 11, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 11, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 11, 2026
In the Linux kernel, the following vulnerability has been resolved: sched/core: Make core-sched flips wait for in-flight selections Core scheduling's pick_next_task() operates on all sibling rqs under one acquisition of the shared core-wide lock. A ->pick_task() that releases the rq lock leaves every sibling __lock momentarily free, letting __sched_core_flip(false) complete mid-selection and rebind rq_lockp() under it. The selection resumes on the split locks, touching sibling state it no longer protects, and __schedule() finally releases a lock that was never taken while leaking the one that was. Count in-flight core-wide selections in the leader's rq->core_pick_in_flight and make __sched_core_flip() wait for the count to drain. The count only changes under the shared lock, which the flip holds while sampling, so no other ordering is needed. The wait can repeat while selections overlap, but the flip backs off between samples and flips are rare cookie-lifetime events. sched_core_cpu_deactivate() moves the count to the new leader - a stale copy left behind would bias it forever if that CPU later returns as its own leader.
Quoted source text, attributed separately from HOL analysis.