<?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>Wed, 30 Sep 2026 12:51:02 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-53175 — ipc: fix memleak if msg_init_ns failed in create_ipc_ns</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2024-53175</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;ipc: fix memleak if msg_init_ns failed in create_ipc_ns&lt;/p&gt;
&lt;p&gt;Percpu memory allocation may failed during create_ipc_ns however this
fail is not handled properly since ipc sysctls and mq sysctls is not
released properly. Fix this by release these two resource when failure.&lt;/p&gt;
&lt;p&gt;Here is the kmemleak stack when percpu failed:&lt;/p&gt;
&lt;p&gt;unreferenced object 0xffff88819de2a600 (size 512):
  comm &amp;#34;shmem_2nstest&amp;#34;, pid 120711, jiffies 4300542254
  hex dump (first 32 bytes):
    60 aa 9d 84 ff ff ff ff fc 18 48 b2 84 88 ff ff  `.........H.....
    04 00 00 00 a4 01 00 00 20 e4 56 81 ff ff ff ff  ........ .V.....
  backtrace (crc be7cba35):
    [&amp;lt;ffffffff81b43f83&amp;gt;] __kmalloc_node_track_caller_noprof+0x333/0x420
    [&amp;lt;ffffffff81a52e56&amp;gt;] kmemdup_noprof+0x26/0x50
    [&amp;lt;ffffffff821b2f37&amp;gt;] setup_mq_sysctls+0x57/0x1d0
    [&amp;lt;ffffffff821b29cc&amp;gt;] copy_ipcs+0x29c/0x3b0
    [&amp;lt;ffffffff815d6a10&amp;gt;] create_new_namespaces+0x1d0/0x920
    [&amp;lt;ffffffff815d7449&amp;gt;] copy_namespaces+0x2e9/0x3e0
    [&amp;lt;ffffffff815458f3&amp;gt;] copy_process+0x29f3/0x7ff0
    [&amp;lt;ffffffff8154b080&amp;gt;] kernel_clone+0xc0/0x650
    [&amp;lt;ffffffff8154b6b1&amp;gt;] __do_sys_clone+0xa1/0xe0
    [&amp;lt;ffffffff843df8ff&amp;gt;] do_syscall_64+0xbf/0x1c0
    [&amp;lt;ffffffff846000b0&amp;gt;] entry_SYSCALL_64_after_hwframe+0x4b/0x53&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;ipc: fix memleak if msg_init_ns failed in create_ipc_ns&lt;/p&gt;
&lt;p&gt;Percpu memory allocation may failed during create_ipc_ns however this
fail is not handled properly since ipc sysctls and mq sysctls is not
released properly. Fix this by release these two resource when failure.&lt;/p&gt;
&lt;p&gt;Here is the kmemleak stack when percpu failed:&lt;/p&gt;
&lt;p&gt;unreferenced object 0xffff88819de2a600 (size 512):
  comm &amp;#34;shmem_2nstest&amp;#34;, pid 120711, jiffies 4300542254
  hex dump (first 32 bytes):
    60 aa 9d 84 ff ff ff ff fc 18 48 b2 84 88 ff ff  `.........H.....
    04 00 00 00 a4 01 00 00 20 e4 56 81 ff ff ff ff  ........ .V.....
  backtrace (crc be7cba35):
    [&amp;lt;ffffffff81b43f83&amp;gt;] __kmalloc_node_track_caller_noprof+0x333/0x420
    [&amp;lt;ffffffff81a52e56&amp;gt;] kmemdup_noprof+0x26/0x50
    [&amp;lt;ffffffff821b2f37&amp;gt;] setup_mq_sysctls+0x57/0x1d0
    [&amp;lt;ffffffff821b29cc&amp;gt;] copy_ipcs+0x29c/0x3b0
    [&amp;lt;ffffffff815d6a10&amp;gt;] create_new_namespaces+0x1d0/0x920
    [&amp;lt;ffffffff815d7449&amp;gt;] copy_namespaces+0x2e9/0x3e0
    [&amp;lt;ffffffff815458f3&amp;gt;] copy_process+0x29f3/0x7ff0
    [&amp;lt;ffffffff8154b080&amp;gt;] kernel_clone+0xc0/0x650
    [&amp;lt;ffffffff8154b6b1&amp;gt;] __do_sys_clone+0xa1/0xe0
    [&amp;lt;ffffffff843df8ff&amp;gt;] do_syscall_64+0xbf/0x1c0
    [&amp;lt;ffffffff846000b0&amp;gt;] entry_SYSCALL_64_after_hwframe+0x4b/0x53&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2024-53175</guid>
    </item>
  </channel>
</rss>
