<?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>Tue, 29 Sep 2026 20:39:16 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-56584 — io_uring/tctx: work around xa_store() allocation error issue</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2024-56584</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/tctx: work around xa_store() allocation error issue&lt;/p&gt;
&lt;p&gt;syzbot triggered the following WARN_ON:&lt;/p&gt;
&lt;p&gt;WARNING: CPU: 0 PID: 16 at io_uring/tctx.c:51 __io_uring_free+0xfa/0x140 io_uring/tctx.c:51&lt;/p&gt;
&lt;p&gt;which is the&lt;/p&gt;
&lt;p&gt;WARN_ON_ONCE(!xa_empty(&amp;amp;tctx-&amp;gt;xa));&lt;/p&gt;
&lt;p&gt;sanity check in __io_uring_free() when a io_uring_task is going through
its final put. The syzbot test case includes injecting memory allocation
failures, and it very much looks like xa_store() can fail one of its
memory allocations and end up with -&amp;gt;head being non-NULL even though no
entries exist in the xarray.&lt;/p&gt;
&lt;p&gt;Until this issue gets sorted out, work around it by attempting to
iterate entries in our xarray, and WARN_ON_ONCE() if one is found.&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/tctx: work around xa_store() allocation error issue&lt;/p&gt;
&lt;p&gt;syzbot triggered the following WARN_ON:&lt;/p&gt;
&lt;p&gt;WARNING: CPU: 0 PID: 16 at io_uring/tctx.c:51 __io_uring_free+0xfa/0x140 io_uring/tctx.c:51&lt;/p&gt;
&lt;p&gt;which is the&lt;/p&gt;
&lt;p&gt;WARN_ON_ONCE(!xa_empty(&amp;amp;tctx-&amp;gt;xa));&lt;/p&gt;
&lt;p&gt;sanity check in __io_uring_free() when a io_uring_task is going through
its final put. The syzbot test case includes injecting memory allocation
failures, and it very much looks like xa_store() can fail one of its
memory allocations and end up with -&amp;gt;head being non-NULL even though no
entries exist in the xarray.&lt;/p&gt;
&lt;p&gt;Until this issue gets sorted out, work around it by attempting to
iterate entries in our xarray, and WARN_ON_ONCE() if one is found.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2024-56584</guid>
    </item>
  </channel>
</rss>
