<?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>Fri, 02 Oct 2026 23:25:26 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-43392</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-43392</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2026-43392</guid>
    </item>
    <item>
      <title>EUVD-2026-315917</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-315917</link>
      <description>EUVD-2026-315917</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-315917</guid>
    </item>
    <item>
      <title>fkie_cve-2026-43392</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-43392</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;sched_ext: Fix starvation of scx_enable() under fair-class saturation&lt;/p&gt;
&lt;p&gt;During scx_enable(), the READY -&amp;gt; ENABLED task switching loop changes the
calling thread&amp;#39;s sched_class from fair to ext. Since fair has higher
priority than ext, saturating fair-class workloads can indefinitely starve
the enable thread, hanging the system. This was introduced when the enable
path switched from preempt_disable() to scx_bypass() which doesn&amp;#39;t protect
against fair-class starvation. Note that the original preempt_disable()
protection wasn&amp;#39;t complete either - in partial switch modes, the calling
thread could still be starved after preempt_enable() as it may have been
switched to ext class.&lt;/p&gt;
&lt;p&gt;Fix it by offloading the enable body to a dedicated system-wide RT
(SCHED_FIFO) kthread which cannot be starved by either fair or ext class
tasks. scx_enable() lazily creates the kthread on first use and passes the
ops pointer through a struct scx_enable_cmd containing the kthread_work,
then synchronously waits for completion.&lt;/p&gt;
&lt;p&gt;The workfn runs on a different kthread from sch-&amp;gt;helper (which runs
disable_work), so it can safely flush disable_work on the error path
without deadlock.&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: Fix starvation of scx_enable() under fair-class saturation&lt;/p&gt;
&lt;p&gt;During scx_enable(), the READY -&amp;gt; ENABLED task switching loop changes the
calling thread&amp;#39;s sched_class from fair to ext. Since fair has higher
priority than ext, saturating fair-class workloads can indefinitely starve
the enable thread, hanging the system. This was introduced when the enable
path switched from preempt_disable() to scx_bypass() which doesn&amp;#39;t protect
against fair-class starvation. Note that the original preempt_disable()
protection wasn&amp;#39;t complete either - in partial switch modes, the calling
thread could still be starved after preempt_enable() as it may have been
switched to ext class.&lt;/p&gt;
&lt;p&gt;Fix it by offloading the enable body to a dedicated system-wide RT
(SCHED_FIFO) kthread which cannot be starved by either fair or ext class
tasks. scx_enable() lazily creates the kthread on first use and passes the
ops pointer through a struct scx_enable_cmd containing the kthread_work,
then synchronously waits for completion.&lt;/p&gt;
&lt;p&gt;The workfn runs on a different kthread from sch-&amp;gt;helper (which runs
disable_work), so it can safely flush disable_work on the error path
without deadlock.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-43392</guid>
    </item>
    <item>
      <title>GHSA-vww6-hvwf-mv33</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-vww6-hvwf-mv33</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;sched_ext: Fix starvation of scx_enable() under fair-class saturation&lt;/p&gt;
&lt;p&gt;During scx_enable(), the READY -&amp;gt; ENABLED task switching loop changes the
calling thread&amp;#39;s sched_class from fair to ext. Since fair has higher
priority than ext, saturating fair-class workloads can indefinitely starve
the enable thread, hanging the system. This was introduced when the enable
path switched from preempt_disable() to scx_bypass() which doesn&amp;#39;t protect
against fair-class starvation. Note that the original preempt_disable()
protection wasn&amp;#39;t complete either - in partial switch modes, the calling
thread could still be starved after preempt_enable() as it may have been
switched to ext class.&lt;/p&gt;
&lt;p&gt;Fix it by offloading the enable body to a dedicated system-wide RT
(SCHED_FIFO) kthread which cannot be starved by either fair or ext class
tasks. scx_enable() lazily creates the kthread on first use and passes the
ops pointer through a struct scx_enable_cmd containing the kthread_work,
then synchronously waits for completion.&lt;/p&gt;
&lt;p&gt;The workfn runs on a different kthread from sch-&amp;gt;helper (which runs
disable_work), so it can safely flush disable_work on the error path
without deadlock.&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: Fix starvation of scx_enable() under fair-class saturation&lt;/p&gt;
&lt;p&gt;During scx_enable(), the READY -&amp;gt; ENABLED task switching loop changes the
calling thread&amp;#39;s sched_class from fair to ext. Since fair has higher
priority than ext, saturating fair-class workloads can indefinitely starve
the enable thread, hanging the system. This was introduced when the enable
path switched from preempt_disable() to scx_bypass() which doesn&amp;#39;t protect
against fair-class starvation. Note that the original preempt_disable()
protection wasn&amp;#39;t complete either - in partial switch modes, the calling
thread could still be starved after preempt_enable() as it may have been
switched to ext class.&lt;/p&gt;
&lt;p&gt;Fix it by offloading the enable body to a dedicated system-wide RT
(SCHED_FIFO) kthread which cannot be starved by either fair or ext class
tasks. scx_enable() lazily creates the kthread on first use and passes the
ops pointer through a struct scx_enable_cmd containing the kthread_work,
then synchronously waits for completion.&lt;/p&gt;
&lt;p&gt;The workfn runs on a different kthread from sch-&amp;gt;helper (which runs
disable_work), so it can safely flush disable_work on the error path
without deadlock.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-vww6-hvwf-mv33</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-43392</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-43392</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 106 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: sched_ext: Fix starvation of scx_enable() under fair-class saturation During scx_enable(), the READY -&amp;gt; ENABLED task switching loop changes the calling thread&amp;#39;s sched_class from fair to ext. Since fair has higher priority than ext, saturating fair-class workloads can indefinitely starve the enable thread, hanging the system. This was introduced when the enable path switched from preempt_disable() to scx_bypass() which doesn&amp;#39;t protect against fair-class starvation. Note that the original preempt_disable() protection wasn&amp;#39;t complete either - in partial switch modes, the calling thread could still be starved after preempt_enable() as it may have been switched to ext class. Fix it by offloading the enable body to a dedicated system-wide RT (SCHED_FIFO) kthread which cannot be starved by either fair or ext class tasks. scx_enable() lazily creates the kthread on first use and passes the ops pointer through a struct scx_enable_cmd containing the kthread_work, then synchronously waits for completion. The workfn runs on a different kthread from sch-&amp;gt;helper (which runs disable_work), so it can safely flush disable_work on the error path without deadlock.&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 106 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: sched_ext: Fix starvation of scx_enable() under fair-class saturation During scx_enable(), the READY -&amp;gt; ENABLED task switching loop changes the calling thread&amp;#39;s sched_class from fair to ext. Since fair has higher priority than ext, saturating fair-class workloads can indefinitely starve the enable thread, hanging the system. This was introduced when the enable path switched from preempt_disable() to scx_bypass() which doesn&amp;#39;t protect against fair-class starvation. Note that the original preempt_disable() protection wasn&amp;#39;t complete either - in partial switch modes, the calling thread could still be starved after preempt_enable() as it may have been switched to ext class. Fix it by offloading the enable body to a dedicated system-wide RT (SCHED_FIFO) kthread which cannot be starved by either fair or ext class tasks. scx_enable() lazily creates the kthread on first use and passes the ops pointer through a struct scx_enable_cmd containing the kthread_work, then synchronously waits for completion. The workfn runs on a different kthread from sch-&amp;gt;helper (which runs disable_work), so it can safely flush disable_work on the error path without deadlock.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-43392</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-1454 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1454</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, Daten zu manipulieren oder offenzulegen oder einen Denial-of-Service-Zustand zu verursachen.&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, Daten zu manipulieren oder offenzulegen oder einen Denial-of-Service-Zustand zu verursachen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1454</guid>
    </item>
  </channel>
</rss>
