<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-08T10:46:38.740843+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/cve-2024-41080</id>
    <title>CVE-2024-41080 — io_uring: fix possible deadlock in io_register_iowq_max_workers()</title>
    <updated>2026-10-08T10:46:38.756471+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Linux</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>io_uring: fix possible deadlock in io_register_iowq_max_workers()</p>
<p>The io_register_iowq_max_workers() function calls io_put_sq_data(),
which acquires the sqd-&gt;lock without releasing the uring_lock.
Similar to the commit 009ad9f0c6ee ("io_uring: drop ctx-&gt;uring_lock
before acquiring sqd-&gt;lock"), this can lead to a potential deadlock
situation.</p>
<p>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.</p>
<p>This change ensures that the locks are acquired in the correct
order, preventing the possibility of a deadlock.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/cve-2024-41080"/>
  </entry>
</feed>
