Look up another CVE · open CVE-2026-74731 in the interactive tracker
CVE-2026-74731
sched_ext: Skip sub-disable teardown for never-linked sub-schedulers
Published 2026-08-22 (2 months ago) by the Linux kernel CNA. Subsystem kernel/sched. Debian urgency: unimportant.
What to do, per Debian release
Debian's own status for CVE-2026-74731 in every release this site tracks, and what each one means in practice. Every status below is the one the Debian Security Team publishes for this CVE. source
| Release | Status | Version | What this means |
|---|---|---|---|
| Debian 12bookworm | not affected | 6.1.190-1 | Nothing to do. bookworm never shipped the vulnerable code. |
| Debian 13trixie | not affected | 6.12.113-1 | Nothing to do. trixie never shipped the vulnerable code. |
| Debian 14forky | fixed | 7.1.9-1 | Update the kernel and reboot. Fixed in 7.1.9-1. A running kernel keeps the old code until the machine restarts. |
| Debian unstablesid | fixed | 7.1.9-1 | Update the kernel and reboot. Fixed in 7.1.9-1. A running kernel keeps the old code until the machine restarts. |
The vulnerability
What the bug is
A sub-scheduler enable can fail before scx_link_sched() links the sched into the hierarchy, e.g. when the parent is already being disabled, and cleanup still runs the full scx_sub_disable(). That is racy against root disable: drain_descendants() is the only ordering between a sub's disable-time task walk and root disable's all-task teardown, and an unlinked sub is invisible to it. Root's teardown can thus run between the never-linked sub's drain and its walk, exiting every task to no scheduler. The walk then trips the membership WARN and re-homes the exited tasks onto the dying hierarchy, a use-after-free. Skip the cgroup ownership reset and the task walk if @sch was never linked, indicated by the empty ->sibling as unlinking only happens later in the same function. The membership WARN remains valid: a linked sub is always waited on by an ancestor's drain.
Where it lives
The fix touches these files. If the subsystem is one you do not use, the practical exposure is lower, though the package is still the vulnerable one.
kernel/sched/ext/ext.c
- What this is
- SCHEDULER - SCHED_EXTMAINTAINERS section matched on kernel/sched/ext/ · sched-ext@lists.linux.dev · Maintained
Show whether Debian builds this, per release
Not established. This site could not find the build rule for the affected file in the kernel trees Debian ships, so it has no answer about whether Debian compiles this code. Read that as unknown, never as absent.
- bookworm, trixie, forky, sid?
- ?
- not established - no Makefile entry for the affected file
Where a release above reads "not established", no build rule for the affected file was found in that release's kernel tree. That is a gap in this lookup, not a finding that the code is absent.
From the configuration Debian publishes for every kernel flavour it builds. It covers only the architectures Debian ships a linux-config package for, and nothing about a kernel you built yourself. Debian's own status above stays authoritative about the source package.MAINTAINERS
Signals
- Published
- 2026-08-22 (2 months ago)source
- CVSS
- 7.8 high
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:Hsource recompute it - Attack vector
- local (AV:L)source
- EPSS
- 0.17%, higher than 5.3% of all CVEssource
- CISA KEV
- not listedthe KEV catalogue
- Debian urgency
- unimportantsource
- Subsystem
- kernel/sched
Upstream fixes
The versions the CNA records as introducing and fixing this, and the commit for each. source
| Introduced | Fixed in | Commit |
|---|---|---|
| 7.1 | 7.1.9 | 6428093a4a98 |
| 7.1 | 7.2 | 8c13364db9c9 |
Why the CNA scored it this way
Quoted from the kernel CNA's own scoring file, word for word. A highlighted metric carries the most severe value CVSS v3.1 defines for it, which is what pushes the score up. source
- AV:LAttack vector, local
- The bug is reached only via local bpf(2) syscalls (BPF_MAP_CREATE/UPDATE_ELEM, BPF_PROG_LOAD, BPF_LINK_CREATE) that register sched_ext_ops struct_ops and invoke scx_enable()/scx_sub_enable_workfn(); per kernel CNA guidance BPF/sched_ext is Local, not network-reachable.
- AC:LAttack complexity, low
- The attacker controls both sides of the race by concurrently attaching a sub-scheduler and closing the root BPF link to trigger scx_root_disable() while never-linked sub cleanup runs scx_sub_disable(); repeated attempts can reliably hit the window between drain_descendants() and the task walk.
- PR:LPrivileges required, low
- Exploitation requires CAP_BPF to create BPF_MAP_TYPE_STRUCT_OPS, load BPF_PROG_TYPE_STRUCT_OPS, and BPF_LINK_CREATE sched_ext; per kernel guidance this is Low because CAP_BPF is obtainable via user namespaces/BPF tokens, not init-namespace root only.
- UI:NUser interaction, none
- No victim interaction is required; the attacker loads root and sub BPF schedulers, targets their cgroup, and closes BPF links from their own processes to orchestrate the concurrent enable-failure and teardown race.
- S:UScope, unchanged
- The use-after-free corrupts kernel scheduler/task state during sched_ext teardown on the same host kernel; this is standard kernel memory corruption and privilege escalation impact, not a VM escape or cross-security-authority boundary.
- C:HConfidentiality impact, high
- Failed never-linked sub cleanup re-homes tasks onto a dying scx_sched hierarchy after root disable frees scheduler state; this use-after-free on scheduler/task metadata can be leveraged for arbitrary kernel memory disclosure per kernel UAF guidance.
- I:HIntegrity impact, high
- The UAF during scx_set_task_sched()/scx_enable_task() on a freed scx_sched corrupts scheduler pointers and task ownership in the system-wide scheduler path, enabling heap corruption and arbitrary kernel write or code execution primitives.
- A:HAvailability impact, high
- The race re-homes tasks onto a tearing-down sched_ext hierarchy, tripping membership WARNs and corrupting scheduler teardown; this causes kernel oops/panic/hang on a system-wide scheduler subsystem, which is High availability impact per kernel guidance.