<?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>Sun, 04 Oct 2026 11:01:30 +0000</lastBuildDate>
    <item>
      <title>bdu:2024-11539</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2024-11539</link>
      <description>bdu:2024-11539</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2024-11539</guid>
    </item>
    <item>
      <title>certfr-2024-avi-0578 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de SUSE. Certaines d'entre elles permettent à un at…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2024-avi-0578</link>
      <description>certfr-2024-avi-0578</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2024-avi-0578</guid>
    </item>
    <item>
      <title>EUVD-2026-344519</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-344519</link>
      <description>EUVD-2026-344519</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-344519</guid>
    </item>
    <item>
      <title>fkie_cve-2021-47577</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2021-47577</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;io-wq: check for wq exit after adding new worker task_work&lt;/p&gt;
&lt;p&gt;We check IO_WQ_BIT_EXIT before attempting to create a new worker, and
wq exit cancels pending work if we have any. But it&amp;#39;s possible to have
a race between the two, where creation checks exit finding it not set,
but we&amp;#39;re in the process of exiting. The exit side will cancel pending
creation task_work, but there&amp;#39;s a gap where we add task_work after we&amp;#39;ve
canceled existing creations at exit time.&lt;/p&gt;
&lt;p&gt;Fix this by checking the EXIT bit post adding the creation task_work.
If it&amp;#39;s set, run the same cancelation that exit does.&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;io-wq: check for wq exit after adding new worker task_work&lt;/p&gt;
&lt;p&gt;We check IO_WQ_BIT_EXIT before attempting to create a new worker, and
wq exit cancels pending work if we have any. But it&amp;#39;s possible to have
a race between the two, where creation checks exit finding it not set,
but we&amp;#39;re in the process of exiting. The exit side will cancel pending
creation task_work, but there&amp;#39;s a gap where we add task_work after we&amp;#39;ve
canceled existing creations at exit time.&lt;/p&gt;
&lt;p&gt;Fix this by checking the EXIT bit post adding the creation task_work.
If it&amp;#39;s set, run the same cancelation that exit does.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2021-47577</guid>
    </item>
    <item>
      <title>GHSA-5c74-rw46-pr2c</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-5c74-rw46-pr2c</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;io-wq: check for wq exit after adding new worker task_work&lt;/p&gt;
&lt;p&gt;We check IO_WQ_BIT_EXIT before attempting to create a new worker, and
wq exit cancels pending work if we have any. But it&amp;#39;s possible to have
a race between the two, where creation checks exit finding it not set,
but we&amp;#39;re in the process of exiting. The exit side will cancel pending
creation task_work, but there&amp;#39;s a gap where we add task_work after we&amp;#39;ve
canceled existing creations at exit time.&lt;/p&gt;
&lt;p&gt;Fix this by checking the EXIT bit post adding the creation task_work.
If it&amp;#39;s set, run the same cancelation that exit does.&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;io-wq: check for wq exit after adding new worker task_work&lt;/p&gt;
&lt;p&gt;We check IO_WQ_BIT_EXIT before attempting to create a new worker, and
wq exit cancels pending work if we have any. But it&amp;#39;s possible to have
a race between the two, where creation checks exit finding it not set,
but we&amp;#39;re in the process of exiting. The exit side will cancel pending
creation task_work, but there&amp;#39;s a gap where we add task_work after we&amp;#39;ve
canceled existing creations at exit time.&lt;/p&gt;
&lt;p&gt;Fix this by checking the EXIT bit post adding the creation task_work.
If it&amp;#39;s set, run the same cancelation that exit does.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-5c74-rw46-pr2c</guid>
    </item>
    <item>
      <title>SUSE-SU-2024:2372-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2024:2372-1</link>
      <description>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/suse-su-2024:2372-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2021-47577</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2021-47577</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe and 112 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: io-wq: check for wq exit after adding new worker task_work We check IO_WQ_BIT_EXIT before attempting to create a new worker, and wq exit cancels pending work if we have any. But it&amp;#39;s possible to have a race between the two, where creation checks exit finding it not set, but we&amp;#39;re in the process of exiting. The exit side will cancel pending creation task_work, but there&amp;#39;s a gap where we add task_work after we&amp;#39;ve canceled existing creations at exit time. Fix this by checking the EXIT bit post adding the creation task_work. If it&amp;#39;s set, run the same cancelation that exit does.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe and 112 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: io-wq: check for wq exit after adding new worker task_work We check IO_WQ_BIT_EXIT before attempting to create a new worker, and wq exit cancels pending work if we have any. But it&amp;#39;s possible to have a race between the two, where creation checks exit finding it not set, but we&amp;#39;re in the process of exiting. The exit side will cancel pending creation task_work, but there&amp;#39;s a gap where we add task_work after we&amp;#39;ve canceled existing creations at exit time. Fix this by checking the EXIT bit post adding the creation task_work. If it&amp;#39;s set, run the same cancelation that exit does.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2021-47577</guid>
    </item>
    <item>
      <title>WID-SEC-W-2024-1418 — Linux Kernel: Mehrere Schwachstellen ermöglichen nicht spezifizierten Angriff</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2024-1418</link>
      <description>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2024-1418</guid>
    </item>
  </channel>
</rss>
