CVE-2026-43392

sched_ext: Fix starvation of scx_enable() under fair-class saturation

Published May 8, 2026 CVSS 3.1 · 5.5 Medium EPSS < 1% KEV · Not listed
Description
In the Linux kernel, the following vulnerability has been resolved:

sched_ext: Fix starvation of scx_enable() under fair-class saturation

During scx_enable(), the READY -> ENABLED task switching loop changes the
calling thread's sched_class from fair to ext. Since fair has higher
priority than ext, saturating fair-class workloads can indefinitely starve
the enable thread, hanging the system. This was introduced when the enable
path switched from preempt_disable() to scx_bypass() which doesn't protect
against fair-class starvation. Note that the original preempt_disable()
protection wasn't complete either - in partial switch modes, the calling
thread could still be starved after preempt_enable() as it may have been
switched to ext class.

Fix it by offloading the enable body to a dedicated system-wide RT
(SCHED_FIFO) kthread which cannot be starved by either fair or ext class
tasks. scx_enable() lazily creates the kthread on first use and passes the
ops pointer through a struct scx_enable_cmd containing the kthread_work,
then synchronously waits for completion.

The workfn runs on a different kthread from sch->helper (which runs
disable_work), so it can safely flush disable_work on the error path
without deadlock.

Analysis

AI-generated

Technical impact

The Linux kernel’s scx_enable() routine changes a thread’s scheduling class from fair to ext while it attempts to enable extended‑class (scx) functionality. This vulnerability reflects the weakness type CWE‑821, a resource lock during computation that can result in starvation. Because fair scheduling has a higher priority than ext, workloads that saturate fair‑class tasks can starve the enable thread, causing the system to hang. This issue was introduced when the code was switched from preempt_disable() to scx_bypass(), which does not guard against such starvation. The patch solves the problem by offloading the enable work to a dedicated system‑wide real‑time (SCHED_FIFO) kernel thread that cannot be starved by either class. The vulnerability can lead to a permanent system halt until a reboot.

Affected Systems

All Linux kernel builds that contain the unpatched scx_enable() logic are affected, regardless of distribution or architecture. The available kernel version data indicates that all released 6.12 release candidates, 7.0 release candidates, and the generic Linux kernel are susceptible. Any system running a kernel before the commit that introduced the dedicated real‑time thread for scx_enable() is potentially vulnerable.

Risk and Exploitability

The CVSS v3.1 score is 5.5, reflecting a moderate severity that results in denial of service. The EPSS score of less than 1% indicates a very low but nonzero likelihood that the vulnerability will be actively exploited. It is not listed in CISA’s KEV catalog, so no widespread exploitation records are known. The attack vector likely requires the attacker to saturate fair‑class workloads, for example by launching an excessive number of high‑priority tasks; this is inferred from the description and is not explicitly documented as a proven exploitation method in the CVE record.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Apply a kernel update that includes the commit implementing the dedicated real‑time thread for scx_enable().
  • Reboot the system so that the updated kernel image and scheduler code are loaded.
  • As a temporary measure, limit the number or priority of fair‑class tasks or apply cgroup restrictions to reduce the likelihood of fair‑class saturation until a patch can be applied.

Generated by OpenCVE AI on May 26, 2026 at 17:35 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Weaknesses NVD-CWE-noinfo
CPEs cpe:2.3:o:linux:linux_kernel:6.12:-:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:6.12:rc2:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:6.12:rc3:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:6.12:rc4:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:6.12:rc5:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:6.12:rc6:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:6.12:rc7:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:7.0:rc1:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:7.0:rc2:*:*:*:*:*:*
Metrics cvssV3_1

{'score': 5.5, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H'}

Type Values Removed Values Added
Weaknesses CWE-399
CWE-400
Type Values Removed Values Added
Weaknesses CWE-399
CWE-400
Type Values Removed Values Added
Description In the Linux kernel, the following vulnerability has been resolved: sched_ext: Fix starvation of scx_enable() under fair-class saturation During scx_enable(), the READY -> ENABLED task switching loop changes the calling thread's sched_class from fair to ext. Since fair has higher priority than ext, saturating fair-class workloads can indefinitely starve the enable thread, hanging the system. This was introduced when the enable path switched from preempt_disable() to scx_bypass() which doesn't protect against fair-class starvation. Note that the original preempt_disable() protection wasn't complete either - in partial switch modes, the calling thread could still be starved after preempt_enable() as it may have been switched to ext class. Fix it by offloading the enable body to a dedicated system-wide RT (SCHED_FIFO) kthread which cannot be starved by either fair or ext class tasks. scx_enable() lazily creates the kthread on first use and passes the ops pointer through a struct scx_enable_cmd containing the kthread_work, then synchronously waits for completion. The workfn runs on a different kthread from sch->helper (which runs disable_work), so it can safely flush disable_work on the error path without deadlock.
Title sched_ext: Fix starvation of scx_enable() under fair-class saturation
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References
Weaknesses

Sources

Status
PUBLISHED
Assigner
Linux
Published
Updated
May 11, 2026, 10:23 PM
Reserved
May 1, 2026, 2:12 PM
Status
Analyzed
Published
May 8, 2026, 3:16 PM
Modified
Nov 11, 2026, 8:10 PM
Severity
Public date
May 8, 2026, 12:00 AM