<?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 19:28:38 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-74593</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-74593</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:stream: linux-lts&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2026-74593</guid>
    </item>
    <item>
      <title>EUVD-2026-357923</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-357923</link>
      <description>EUVD-2026-357923</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-357923</guid>
    </item>
    <item>
      <title>fkie_cve-2026-74593</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-74593</link>
      <description>&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;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://cve.radiocsirt.org/vuln/fkie_cve-2026-74593</guid>
    </item>
    <item>
      <title>GHSA-jp6g-jm55-gwj8</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-jp6g-jm55-gwj8</link>
      <description>&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;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://cve.radiocsirt.org/vuln/ghsa-jp6g-jm55-gwj8</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-74593</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-74593</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 117 more&lt;/p&gt;
&lt;p&gt;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&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. 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; 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 117 more&lt;/p&gt;
&lt;p&gt;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&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. 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://cve.radiocsirt.org/vuln/ubuntu-cve-2026-74593</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>
