Bug 2513236 (CVE-2026-68421) - CVE-2026-68421 kernel: sched_ext: Don't warn on core-sched forced idle in put_prev_task_scx()
Summary: CVE-2026-68421 kernel: sched_ext: Don't warn on core-sched forced idle in put...
Keywords:
Status: NEW
Alias: CVE-2026-68421
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-08-10 12:26 UTC by OSIDB Bzimport
Modified: 2026-08-13 19:44 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-08-10 12:26:22 UTC
In the Linux kernel, the following vulnerability has been resolved:

sched_ext: Don't warn on core-sched forced idle in put_prev_task_scx()

put_prev_task_scx() warns when a runnable task drops to a lower sched_class
without SCX_OPS_ENQ_LAST, on the assumption that balance_one() would have
kept it running. Core scheduling breaks that: a forced-idle SMT sibling
reschedules through the core_pick fast path in pick_next_task(), which skips
pick_task_scx() and thus balance_one(), so a runnable task can drop to idle
with ENQ_LAST unset.

Gate the warning on sched_cpu_cookie_match(): a cookie mismatch means core
scheduling forced the idle, while a match (or core scheduling off) still
catches a genuine missing-ENQ_LAST drop.


Note You need to log in before you can comment on or make changes to this bug.