<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://vulnerability.circl.lu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Thu, 01 Oct 2026 05:34:14 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-74593 — sched_ext: Take cgroup_lock() first in scx_cgroup_lock()</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-74593</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;sched_ext: Take cgroup_lock() first in scx_cgroup_lock()&lt;/p&gt;
&lt;p&gt;scx_cgroup_lock() write-locks scx_cgroup_ops_rwsem and then takes
cgroup_lock(), which can deadlock through kernfs:&lt;/p&gt;
&lt;p&gt;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()&lt;/p&gt;
&lt;p&gt;The enable path waits for the rmdir to release cgroup_mutex. The rmdir,
deactivating the cpu controller&amp;#39;s files, waits in kernfs_drain() for the
write&amp;#39;s active reference. The write, in scx_group_set_weight(), waits for
the rwsem behind the pending writer.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;sched_ext: Take cgroup_lock() first in scx_cgroup_lock()&lt;/p&gt;
&lt;p&gt;scx_cgroup_lock() write-locks scx_cgroup_ops_rwsem and then takes
cgroup_lock(), which can deadlock through kernfs:&lt;/p&gt;
&lt;p&gt;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()&lt;/p&gt;
&lt;p&gt;The enable path waits for the rmdir to release cgroup_mutex. The rmdir,
deactivating the cpu controller&amp;#39;s files, waits in kernfs_drain() for the
write&amp;#39;s active reference. The write, in scx_group_set_weight(), waits for
the rwsem behind the pending writer.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-74593</guid>
    </item>
  </channel>
</rss>
