<?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 22:05:38 +0000</lastBuildDate>
    <item>
      <title>CVE-2022-50639 — io-wq: Fix memory leak in worker creation</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2022-50639</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: Fix memory leak in worker creation&lt;/p&gt;
&lt;p&gt;If the CPU mask allocation for a node fails, then the memory allocated for
the &amp;#39;io_wqe&amp;#39; struct of the current node doesn&amp;#39;t get freed on the error
handling path, since it has not yet been added to the &amp;#39;wqes&amp;#39; array.&lt;/p&gt;
&lt;p&gt;This was spotted when fuzzing v6.1-rc1 with Syzkaller:
BUG: memory leak
unreferenced object 0xffff8880093d5000 (size 1024):
  comm &amp;#34;syz-executor.2&amp;#34;, pid 7701, jiffies 4295048595 (age 13.900s)
  hex dump (first 32 bytes):
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
  backtrace:
    [&amp;lt;00000000cb463369&amp;gt;] __kmem_cache_alloc_node+0x18e/0x720
    [&amp;lt;00000000147a3f9c&amp;gt;] kmalloc_node_trace+0x2a/0x130
    [&amp;lt;000000004e107011&amp;gt;] io_wq_create+0x7b9/0xdc0
    [&amp;lt;00000000c38b2018&amp;gt;] io_uring_alloc_task_context+0x31e/0x59d
    [&amp;lt;00000000867399da&amp;gt;] __io_uring_add_tctx_node.cold+0x19/0x1ba
    [&amp;lt;000000007e0e7a79&amp;gt;] io_uring_setup.cold+0x1b80/0x1dce
    [&amp;lt;00000000b545e9f6&amp;gt;] __x64_sys_io_uring_setup+0x5d/0x80
    [&amp;lt;000000008a8a7508&amp;gt;] do_syscall_64+0x5d/0x90
    [&amp;lt;000000004ac08bec&amp;gt;] entry_SYSCALL_64_after_hwframe+0x63/0xcd&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: Fix memory leak in worker creation&lt;/p&gt;
&lt;p&gt;If the CPU mask allocation for a node fails, then the memory allocated for
the &amp;#39;io_wqe&amp;#39; struct of the current node doesn&amp;#39;t get freed on the error
handling path, since it has not yet been added to the &amp;#39;wqes&amp;#39; array.&lt;/p&gt;
&lt;p&gt;This was spotted when fuzzing v6.1-rc1 with Syzkaller:
BUG: memory leak
unreferenced object 0xffff8880093d5000 (size 1024):
  comm &amp;#34;syz-executor.2&amp;#34;, pid 7701, jiffies 4295048595 (age 13.900s)
  hex dump (first 32 bytes):
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
  backtrace:
    [&amp;lt;00000000cb463369&amp;gt;] __kmem_cache_alloc_node+0x18e/0x720
    [&amp;lt;00000000147a3f9c&amp;gt;] kmalloc_node_trace+0x2a/0x130
    [&amp;lt;000000004e107011&amp;gt;] io_wq_create+0x7b9/0xdc0
    [&amp;lt;00000000c38b2018&amp;gt;] io_uring_alloc_task_context+0x31e/0x59d
    [&amp;lt;00000000867399da&amp;gt;] __io_uring_add_tctx_node.cold+0x19/0x1ba
    [&amp;lt;000000007e0e7a79&amp;gt;] io_uring_setup.cold+0x1b80/0x1dce
    [&amp;lt;00000000b545e9f6&amp;gt;] __x64_sys_io_uring_setup+0x5d/0x80
    [&amp;lt;000000008a8a7508&amp;gt;] do_syscall_64+0x5d/0x90
    [&amp;lt;000000004ac08bec&amp;gt;] entry_SYSCALL_64_after_hwframe+0x63/0xcd&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2022-50639</guid>
    </item>
  </channel>
</rss>
