<?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>Tue, 29 Sep 2026 17:56:02 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-74731 — sched_ext: Skip sub-disable teardown for never-linked sub-schedulers</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-74731</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: Skip sub-disable teardown for never-linked sub-schedulers&lt;/p&gt;
&lt;p&gt;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().&lt;/p&gt;
&lt;p&gt;That is racy against root disable: drain_descendants() is the only ordering
between a sub&amp;#39;s disable-time task walk and root disable&amp;#39;s all-task teardown,
and an unlinked sub is invisible to it. Root&amp;#39;s teardown can thus run between
the never-linked sub&amp;#39;s drain and its walk, exiting every task to no
scheduler.&lt;/p&gt;
&lt;p&gt;The walk then trips the membership WARN and re-homes the exited tasks onto
the dying hierarchy, a use-after-free.&lt;/p&gt;
&lt;p&gt;Skip the cgroup ownership reset and the task walk if @sch was never linked,
indicated by the empty -&amp;gt;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&amp;#39;s drain.&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: Skip sub-disable teardown for never-linked sub-schedulers&lt;/p&gt;
&lt;p&gt;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().&lt;/p&gt;
&lt;p&gt;That is racy against root disable: drain_descendants() is the only ordering
between a sub&amp;#39;s disable-time task walk and root disable&amp;#39;s all-task teardown,
and an unlinked sub is invisible to it. Root&amp;#39;s teardown can thus run between
the never-linked sub&amp;#39;s drain and its walk, exiting every task to no
scheduler.&lt;/p&gt;
&lt;p&gt;The walk then trips the membership WARN and re-homes the exited tasks onto
the dying hierarchy, a use-after-free.&lt;/p&gt;
&lt;p&gt;Skip the cgroup ownership reset and the task walk if @sch was never linked,
indicated by the empty -&amp;gt;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&amp;#39;s drain.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-74731</guid>
    </item>
  </channel>
</rss>
