CVE-2026-74593
Last modified
CVE-2026-74593 is a vulnerability of currently unknown severity. 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.
Description
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.
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= a5bd6ba30b3364354269b81ac55c2edca9a96d6d, < 2ca6b43edf83f8fc368cc3094ee5f3b1e8e0b0f0; >= a5bd6ba30b3364354269b81ac55c2edca9a96d6d, < a054c9ffa9b7a0dffb763837b91ac9d381ec6d10; >= a5bd6ba30b3364354269b81ac55c2edca9a96d6d, < 5f8b69642d18e1f3e11996707842ac530444e959 |
| Linux | Linux | 6.18 |
References
Timeline
- Published
- Last Modified
- Status
- Received
Frequently Asked Questions
What is CVE-2026-74593?
How severe is CVE-2026-74593?
How do I fix CVE-2026-74593?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-74588In the Linux kernel, the following vulnerability has been re…
- CVE-2026-74589In the Linux kernel, the following vulnerability has been re…
- CVE-2026-7459The Simple History – Track, Log, and Audit WordPress Changes…7.5
- CVE-2026-74590In the Linux kernel, the following vulnerability has been re…
- CVE-2026-74591In the Linux kernel, the following vulnerability has been re…
- CVE-2026-74592In the Linux kernel, the following vulnerability has been re…
- CVE-2026-74594In the Linux kernel, the following vulnerability has been re…
- CVE-2026-74595In the Linux kernel, the following vulnerability has been re…
- CVE-2026-74596In the Linux kernel, the following vulnerability has been re…
- CVE-2026-74597In the Linux kernel, the following vulnerability has been re…
- CVE-2026-74598In the Linux kernel, the following vulnerability has been re…
- CVE-2026-74599In the Linux kernel, the following vulnerability has been re…
Are you affected by CVE-2026-74593?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
