Bug 2521403 (CVE-2026-74593) - CVE-2026-74593 kernel: sched_ext: Take cgroup_lock() first in scx_cgroup_lock()
Summary: CVE-2026-74593 kernel: sched_ext: Take cgroup_lock() first in scx_cgroup_lock()
Keywords:
Status: NEW
Alias: CVE-2026-74593
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-08-22 15:43 UTC by OSIDB Bzimport
Modified: 2026-08-24 11:32 UTC (History)
2 users (show)

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


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-08-22 15:43:52 UTC
In the Linux kernel, the following vulnerability has been resolved:

sched_ext: Take cgroup_lock() first in scx_cgroup_lock()

scx_cgroup_lock() write-locks scx_cgroup_ops_rwsem and then takes
cgroup_lock(), which can deadlock through kernfs:

  scx enable/disable         cgroup rmdir           cpu.weight write
  ------------------         ------------           ----------------
                             cgroup_lock()
  percpu_down_write(rwsem)
  cgroup_lock()
                                                    kernfs_get_active()
                                                    percpu_down_read(rwsem)
                             kernfs_drain()

The enable path waits for the rmdir to release cgroup_mutex. The rmdir,
deactivating the cpu controller's files, waits in kernfs_drain() for the
write's active reference. The write, in scx_group_set_weight(), waits for
the rwsem behind the pending writer.

Take cgroup_lock() first. The set_* paths take no cgroup locks inside the
read side, so a pending write-lock then only waits for read sections that
always run to completion, and no dependency from the rwsem back to
cgroup_mutex remains.

Comment 1 Mauro Matteo Cascella 2026-08-24 11:29:35 UTC
Upstream advisory:
https://lore.kernel.org/linux-cve-announce/2026082213-CVE-2026-74593-f241@gregkh/T


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