<?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>Thu, 08 Oct 2026 06:57:49 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-41080 — io_uring: fix possible deadlock in io_register_iowq_max_workers()</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2024-41080</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_uring: fix possible deadlock in io_register_iowq_max_workers()&lt;/p&gt;
&lt;p&gt;The io_register_iowq_max_workers() function calls io_put_sq_data(),
which acquires the sqd-&amp;gt;lock without releasing the uring_lock.
Similar to the commit 009ad9f0c6ee (&amp;#34;io_uring: drop ctx-&amp;gt;uring_lock
before acquiring sqd-&amp;gt;lock&amp;#34;), this can lead to a potential deadlock
situation.&lt;/p&gt;
&lt;p&gt;To resolve this issue, the uring_lock is released before calling
io_put_sq_data(), and then it is re-acquired after the function call.&lt;/p&gt;
&lt;p&gt;This change ensures that the locks are acquired in the correct
order, preventing the possibility of a deadlock.&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_uring: fix possible deadlock in io_register_iowq_max_workers()&lt;/p&gt;
&lt;p&gt;The io_register_iowq_max_workers() function calls io_put_sq_data(),
which acquires the sqd-&amp;gt;lock without releasing the uring_lock.
Similar to the commit 009ad9f0c6ee (&amp;#34;io_uring: drop ctx-&amp;gt;uring_lock
before acquiring sqd-&amp;gt;lock&amp;#34;), this can lead to a potential deadlock
situation.&lt;/p&gt;
&lt;p&gt;To resolve this issue, the uring_lock is released before calling
io_put_sq_data(), and then it is re-acquired after the function call.&lt;/p&gt;
&lt;p&gt;This change ensures that the locks are acquired in the correct
order, preventing the possibility of a deadlock.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2024-41080</guid>
    </item>
  </channel>
</rss>
