<?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>Fri, 02 Oct 2026 18:06:55 +0000</lastBuildDate>
    <item>
      <title>CVE-2023-53136 — af_unix: fix struct pid leaks in OOB support</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2023-53136</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;af_unix: fix struct pid leaks in OOB support&lt;/p&gt;
&lt;p&gt;syzbot reported struct pid leak [1].&lt;/p&gt;
&lt;p&gt;Issue is that queue_oob() calls maybe_add_creds() which potentially
holds a reference on a pid.&lt;/p&gt;
&lt;p&gt;But skb-&amp;gt;destructor is not set (either directly or by calling
unix_scm_to_skb())&lt;/p&gt;
&lt;p&gt;This means that subsequent kfree_skb() or consume_skb() would leak
this reference.&lt;/p&gt;
&lt;p&gt;In this fix, I chose to fully support scm even for the OOB message.&lt;/p&gt;
&lt;p&gt;[1]
BUG: memory leak
unreferenced object 0xffff8881053e7f80 (size 128):
comm &amp;#34;syz-executor242&amp;#34;, pid 5066, jiffies 4294946079 (age 13.220s)
hex dump (first 32 bytes):
01 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;ffffffff812ae26a&amp;gt;] alloc_pid+0x6a/0x560 kernel/pid.c:180
[&amp;lt;ffffffff812718df&amp;gt;] copy_process+0x169f/0x26c0 kernel/fork.c:2285
[&amp;lt;ffffffff81272b37&amp;gt;] kernel_clone+0xf7/0x610 kernel/fork.c:2684
[&amp;lt;ffffffff812730cc&amp;gt;] __do_sys_clone+0x7c/0xb0 kernel/fork.c:2825
[&amp;lt;ffffffff849ad699&amp;gt;] do_syscall_x64 arch/x86/entry/common.c:50 [inline]
[&amp;lt;ffffffff849ad699&amp;gt;] do_syscall_64+0x39/0xb0 arch/x86/entry/common.c:80
[&amp;lt;ffffffff84a0008b&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;af_unix: fix struct pid leaks in OOB support&lt;/p&gt;
&lt;p&gt;syzbot reported struct pid leak [1].&lt;/p&gt;
&lt;p&gt;Issue is that queue_oob() calls maybe_add_creds() which potentially
holds a reference on a pid.&lt;/p&gt;
&lt;p&gt;But skb-&amp;gt;destructor is not set (either directly or by calling
unix_scm_to_skb())&lt;/p&gt;
&lt;p&gt;This means that subsequent kfree_skb() or consume_skb() would leak
this reference.&lt;/p&gt;
&lt;p&gt;In this fix, I chose to fully support scm even for the OOB message.&lt;/p&gt;
&lt;p&gt;[1]
BUG: memory leak
unreferenced object 0xffff8881053e7f80 (size 128):
comm &amp;#34;syz-executor242&amp;#34;, pid 5066, jiffies 4294946079 (age 13.220s)
hex dump (first 32 bytes):
01 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;ffffffff812ae26a&amp;gt;] alloc_pid+0x6a/0x560 kernel/pid.c:180
[&amp;lt;ffffffff812718df&amp;gt;] copy_process+0x169f/0x26c0 kernel/fork.c:2285
[&amp;lt;ffffffff81272b37&amp;gt;] kernel_clone+0xf7/0x610 kernel/fork.c:2684
[&amp;lt;ffffffff812730cc&amp;gt;] __do_sys_clone+0x7c/0xb0 kernel/fork.c:2825
[&amp;lt;ffffffff849ad699&amp;gt;] do_syscall_x64 arch/x86/entry/common.c:50 [inline]
[&amp;lt;ffffffff849ad699&amp;gt;] do_syscall_64+0x39/0xb0 arch/x86/entry/common.c:80
[&amp;lt;ffffffff84a0008b&amp;gt;] entry_SYSCALL_64_after_hwframe+0x63/0xcd&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2023-53136</guid>
    </item>
  </channel>
</rss>
