<?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://cve.radiocsirt.org</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>Sat, 03 Oct 2026 13:12:06 +0000</lastBuildDate>
    <item>
      <title>Withdrawn: BELL-CVE-2026-74731 — CVE-2026-74731 does not affect BellSoft software</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-74731</link>
      <description>&lt;p&gt;&lt;strong&gt;Withdrawn by the publisher.&lt;/strong&gt;&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Withdrawn by the publisher.&lt;/strong&gt;&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2026-74731</guid>
    </item>
    <item>
      <title>EUVD-2026-358580</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-358580</link>
      <description>EUVD-2026-358580</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-358580</guid>
    </item>
    <item>
      <title>fkie_cve-2026-74731</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-74731</link>
      <description>&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;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://cve.radiocsirt.org/vuln/fkie_cve-2026-74731</guid>
    </item>
    <item>
      <title>GHSA-39hf-rf3c-rjqv</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-39hf-rf3c-rjqv</link>
      <description>&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;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://cve.radiocsirt.org/vuln/ghsa-39hf-rf3c-rjqv</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-74731</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-74731</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 95 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: sched_ext: Skip sub-disable teardown for never-linked sub-schedulers 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&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. 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 -&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; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 95 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: sched_ext: Skip sub-disable teardown for never-linked sub-schedulers 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&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. 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 -&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://cve.radiocsirt.org/vuln/ubuntu-cve-2026-74731</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-2970 — Linux Kernel: Mehrere Schwachstellen ermöglichen nicht spezifizierten Angriff</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2970</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, möglicherweise Sicherheitsmaßnahmen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen oder vertrauliche Informationen offenzulegen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, möglicherweise Sicherheitsmaßnahmen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen oder vertrauliche Informationen offenzulegen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2970</guid>
    </item>
  </channel>
</rss>
