<?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 16:55:05 +0000</lastBuildDate>
    <item>
      <title>CVE-2022-50434 — blk-mq: fix possible memleak when register 'hctx' failed</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2022-50434</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;blk-mq: fix possible memleak when register &amp;#39;hctx&amp;#39; failed&lt;/p&gt;
&lt;p&gt;There&amp;#39;s issue as follows when do fault injection test:
unreferenced object 0xffff888132a9f400 (size 512):
  comm &amp;#34;insmod&amp;#34;, pid 308021, jiffies 4324277909 (age 509.733s)
  hex dump (first 32 bytes):
    00 00 00 00 00 00 00 00 08 f4 a9 32 81 88 ff ff  ...........2....
    08 f4 a9 32 81 88 ff ff 00 00 00 00 00 00 00 00  ...2............
  backtrace:
    [&amp;lt;00000000e8952bb4&amp;gt;] kmalloc_node_trace+0x22/0xa0
    [&amp;lt;00000000f9980e0f&amp;gt;] blk_mq_alloc_and_init_hctx+0x3f1/0x7e0
    [&amp;lt;000000002e719efa&amp;gt;] blk_mq_realloc_hw_ctxs+0x1e6/0x230
    [&amp;lt;000000004f1fda40&amp;gt;] blk_mq_init_allocated_queue+0x27e/0x910
    [&amp;lt;00000000287123ec&amp;gt;] __blk_mq_alloc_disk+0x67/0xf0
    [&amp;lt;00000000a2a34657&amp;gt;] 0xffffffffa2ad310f
    [&amp;lt;00000000b173f718&amp;gt;] 0xffffffffa2af824a
    [&amp;lt;0000000095a1dabb&amp;gt;] do_one_initcall+0x87/0x2a0
    [&amp;lt;00000000f32fdf93&amp;gt;] do_init_module+0xdf/0x320
    [&amp;lt;00000000cbe8541e&amp;gt;] load_module+0x3006/0x3390
    [&amp;lt;0000000069ed1bdb&amp;gt;] __do_sys_finit_module+0x113/0x1b0
    [&amp;lt;00000000a1a29ae8&amp;gt;] do_syscall_64+0x35/0x80
    [&amp;lt;000000009cd878b0&amp;gt;] entry_SYSCALL_64_after_hwframe+0x46/0xb0&lt;/p&gt;
&lt;p&gt;Fault injection context as follows:
 kobject_add
 blk_mq_register_hctx
 blk_mq_sysfs_register
 blk_register_queue
 device_add_disk
 null_add_dev.part.0 [null_blk]&lt;/p&gt;
&lt;p&gt;As &amp;#39;blk_mq_register_hctx&amp;#39; may already add some objects when failed halfway,
but there isn&amp;#39;t do fallback, caller don&amp;#39;t know which objects add f…&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;blk-mq: fix possible memleak when register &amp;#39;hctx&amp;#39; failed&lt;/p&gt;
&lt;p&gt;There&amp;#39;s issue as follows when do fault injection test:
unreferenced object 0xffff888132a9f400 (size 512):
  comm &amp;#34;insmod&amp;#34;, pid 308021, jiffies 4324277909 (age 509.733s)
  hex dump (first 32 bytes):
    00 00 00 00 00 00 00 00 08 f4 a9 32 81 88 ff ff  ...........2....
    08 f4 a9 32 81 88 ff ff 00 00 00 00 00 00 00 00  ...2............
  backtrace:
    [&amp;lt;00000000e8952bb4&amp;gt;] kmalloc_node_trace+0x22/0xa0
    [&amp;lt;00000000f9980e0f&amp;gt;] blk_mq_alloc_and_init_hctx+0x3f1/0x7e0
    [&amp;lt;000000002e719efa&amp;gt;] blk_mq_realloc_hw_ctxs+0x1e6/0x230
    [&amp;lt;000000004f1fda40&amp;gt;] blk_mq_init_allocated_queue+0x27e/0x910
    [&amp;lt;00000000287123ec&amp;gt;] __blk_mq_alloc_disk+0x67/0xf0
    [&amp;lt;00000000a2a34657&amp;gt;] 0xffffffffa2ad310f
    [&amp;lt;00000000b173f718&amp;gt;] 0xffffffffa2af824a
    [&amp;lt;0000000095a1dabb&amp;gt;] do_one_initcall+0x87/0x2a0
    [&amp;lt;00000000f32fdf93&amp;gt;] do_init_module+0xdf/0x320
    [&amp;lt;00000000cbe8541e&amp;gt;] load_module+0x3006/0x3390
    [&amp;lt;0000000069ed1bdb&amp;gt;] __do_sys_finit_module+0x113/0x1b0
    [&amp;lt;00000000a1a29ae8&amp;gt;] do_syscall_64+0x35/0x80
    [&amp;lt;000000009cd878b0&amp;gt;] entry_SYSCALL_64_after_hwframe+0x46/0xb0&lt;/p&gt;
&lt;p&gt;Fault injection context as follows:
 kobject_add
 blk_mq_register_hctx
 blk_mq_sysfs_register
 blk_register_queue
 device_add_disk
 null_add_dev.part.0 [null_blk]&lt;/p&gt;
&lt;p&gt;As &amp;#39;blk_mq_register_hctx&amp;#39; may already add some objects when failed halfway,
but there isn&amp;#39;t do fallback, caller don&amp;#39;t know which objects add f…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2022-50434</guid>
    </item>
  </channel>
</rss>
