<?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>Thu, 01 Oct 2026 00:48:22 +0000</lastBuildDate>
    <item>
      <title>CVE-2021-47577 — io-wq: check for wq exit after adding new worker task_work</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2021-47577</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;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;&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;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://vulnerability.circl.lu/vuln/cve-2021-47577</guid>
    </item>
  </channel>
</rss>
