sched_ext: Replace SCX_RQ_BAL_KEEP with a dispatch verdict return
In the Linux kernel, the following vulnerability has been resolved: sched_ext: Replace SCX_RQ_BAL_KEEP with a dispatch verdict return SCX_RQ_BAL_KEEP tells the pick to keep running the previous task, a leftover from when balancing and picking were separate operations. An rq-level flag only works while dispatches and picks pair up one to one, which core scheduling breaks: selections interleave through dispatch's lock drops and a pick can consume a stale flag, keeping a task that has since been dequeued. Fixing core scheduling support requires the decision to travel with the dispatch that made it. Make scx_dispatch_sched() and balance_one() return an explicit verdict instead and drop the flag's plumbing from the tools autogen enum headers. Also factor the pick-side invocation, its follow-up queueing and the post-dispatch checks out of do_pick_task_scx() into dispatch_pick(). No functional changes intended. v2: Drop the SCX_RQ_BAL_KEEP plumbing from the tools autogen enum headers as well (Andrea).
- Products
- Kernel
- Affected versions
- Not specified
- Fixed versions
- 7.2.4
- CVEs
- CVE-2026-89519
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 3 Nov 2026, 16:16 UTC · Revision 1
Source evidence
sched_ext: Replace SCX_RQ_BAL_KEEP with a dispatch verdict return
core-osv · Original sourcePublished 11 Sept 2026, 19:44 UTC
In the Linux kernel, the following vulnerability has been resolved: sched_ext: Replace SCX_RQ_BAL_KEEP with a dispatch verdict return SCX_RQ_BAL_KEEP tells the pick to keep running the previous task, a leftover from when balancing and picking were separate operations. An rq-level flag only works while dispatches and picks pair up one to one, which core scheduling breaks: selections interleave through dispatch's lock drops and a pick can consume a stale flag, keeping a task that has since been dequeued. Fixing core scheduling support requires the decision to travel with the dispatch that made it. Make scx_dispatch_sched() and balance_one() return an explicit verdict instead and drop the flag's plumbing from the tools autogen enum headers. Also factor the pick-side invocation, its follow-up queueing and the post-dispatch checks out of do_pick_task_scx() into dispatch_pick(). No functional changes intended. v2: Drop the SCX_RQ_BAL_KEEP plumbing from the tools autogen enum headers as well (Andrea).
osv:CVE-2026-89519
Kernel
Fixed versions: 7.2.4
Complete source record
{
"id": "54788af0c90c8caa6480eb71ad7f84ddbc3bfbf64e8321ae1f0ae70478303904",
"url": "https://osv.dev/vulnerability/CVE-2026-89519",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "sched_ext: Replace SCX_RQ_BAL_KEEP with a dispatch verdict return",
"summary": "In the Linux kernel, the following vulnerability has been resolved: sched_ext: Replace SCX_RQ_BAL_KEEP with a dispatch verdict return SCX_RQ_BAL_KEEP tells the pick to keep running the previous task, a leftover from when balancing and picking were separate operations. An rq-level flag only works while dispatches and picks pair up one to one, which core scheduling breaks: selections interleave through dispatch's lock drops and a pick can consume a stale flag, keeping a task that has since been dequeued. Fixing core scheduling support requires the decision to travel with the dispatch that made it. Make scx_dispatch_sched() and balance_one() return an explicit verdict instead and drop the flag's plumbing from the tools autogen enum headers. Also factor the pick-side invocation, its follow-up queueing and the post-dispatch checks out of do_pick_task_scx() into dispatch_pick(). No functional changes intended. v2: Drop the SCX_RQ_BAL_KEEP plumbing from the tools autogen enum headers as well (Andrea).",
"evidence": "osv:CVE-2026-89519",
"products": [
{
"name": {
"value": "Kernel",
"evidence": "/affected/1/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "7.2.4",
"evidence": "/affected/1/ranges"
}
],
"affected_versions": []
}
],
"severity": "unknown",
"structured": {
"id": "CVE-2026-89519",
"aliases": [
"CVE-2026-89519"
],
"affected": [
{
"ranges": [
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "4c95380701f58b8112f0b891de8d160e4199e19d"
},
{
"fixed": "6f1d3bfe54430f8d54e0530a27f2ecbf8466576e"
},
{
"fixed": "ffaab58d217581cb75353168f8812a16e10463fc"
}
]
}
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-89519.json"
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.19.0"
},
{
"fixed": "7.2.4"
}
]
}
],
"package": {
"name": "Kernel",
"ecosystem": "Linux"
},
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-89519.json"
}
}
],
"modified": "2026-10-28T02:30:30.135168170Z",
"provider": "osv",
"references": [
"https://git.kernel.org/stable/c/6f1d3bfe54430f8d54e0530a27f2ecbf8466576e",
"https://git.kernel.org/stable/c/ffaab58d217581cb75353168f8812a16e10463fc",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/89xxx/CVE-2026-89519.json",
"https://nvd.nist.gov/vuln/detail/CVE-2026-89519",
"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
],
"provider_metadata": {
"cna_assigner": "Linux",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/89xxx/CVE-2026-89519.json"
}
},
"related_cves": [
{
"value": "CVE-2026-89519",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": null
},
"source_id": "core-osv",
"document_id": 497241,
"published_at": "2026-09-11T19:44:01.858+00:00"
}