<?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 13:57:07 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-56553 — binder: fix memleak of proc-&gt;delivered_freeze</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2024-56553</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;binder: fix memleak of proc-&amp;gt;delivered_freeze&lt;/p&gt;
&lt;p&gt;If a freeze notification is cleared with BC_CLEAR_FREEZE_NOTIFICATION
before calling binder_freeze_notification_done(), then it is detached
from its reference (e.g. ref-&amp;gt;freeze) but the work remains queued in
proc-&amp;gt;delivered_freeze. This leads to a memory leak when the process
exits as any pending entries in proc-&amp;gt;delivered_freeze are not freed:&lt;/p&gt;
&lt;p&gt;unreferenced object 0xffff38e8cfa36180 (size 64):
    comm &amp;#34;binder-util&amp;#34;, pid 655, jiffies 4294936641
    hex dump (first 32 bytes):
      b8 e9 9e c8 e8 38 ff ff b8 e9 9e c8 e8 38 ff ff  .....8.......8..
      0b 00 00 00 00 00 00 00 3c 1f 4b 00 00 00 00 00  ........&amp;lt;.K.....
    backtrace (crc 95983b32):
      [&amp;lt;000000000d0582cf&amp;gt;] kmemleak_alloc+0x34/0x40
      [&amp;lt;000000009c99a513&amp;gt;] __kmalloc_cache_noprof+0x208/0x280
      [&amp;lt;00000000313b1704&amp;gt;] binder_thread_write+0xdec/0x439c
      [&amp;lt;000000000cbd33bb&amp;gt;] binder_ioctl+0x1b68/0x22cc
      [&amp;lt;000000002bbedeeb&amp;gt;] __arm64_sys_ioctl+0x124/0x190
      [&amp;lt;00000000b439adee&amp;gt;] invoke_syscall+0x6c/0x254
      [&amp;lt;00000000173558fc&amp;gt;] el0_svc_common.constprop.0+0xac/0x230
      [&amp;lt;0000000084f72311&amp;gt;] do_el0_svc+0x40/0x58
      [&amp;lt;000000008b872457&amp;gt;] el0_svc+0x38/0x78
      [&amp;lt;00000000ee778653&amp;gt;] el0t_64_sync_handler+0x120/0x12c
      [&amp;lt;00000000a8ec61bf&amp;gt;] el0t_64_sync+0x190/0x194&lt;/p&gt;
&lt;p&gt;This patch fixes the leak by ensuring that any pending entries in
proc-&amp;gt;delivered_freeze are freed during binder_def…&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;binder: fix memleak of proc-&amp;gt;delivered_freeze&lt;/p&gt;
&lt;p&gt;If a freeze notification is cleared with BC_CLEAR_FREEZE_NOTIFICATION
before calling binder_freeze_notification_done(), then it is detached
from its reference (e.g. ref-&amp;gt;freeze) but the work remains queued in
proc-&amp;gt;delivered_freeze. This leads to a memory leak when the process
exits as any pending entries in proc-&amp;gt;delivered_freeze are not freed:&lt;/p&gt;
&lt;p&gt;unreferenced object 0xffff38e8cfa36180 (size 64):
    comm &amp;#34;binder-util&amp;#34;, pid 655, jiffies 4294936641
    hex dump (first 32 bytes):
      b8 e9 9e c8 e8 38 ff ff b8 e9 9e c8 e8 38 ff ff  .....8.......8..
      0b 00 00 00 00 00 00 00 3c 1f 4b 00 00 00 00 00  ........&amp;lt;.K.....
    backtrace (crc 95983b32):
      [&amp;lt;000000000d0582cf&amp;gt;] kmemleak_alloc+0x34/0x40
      [&amp;lt;000000009c99a513&amp;gt;] __kmalloc_cache_noprof+0x208/0x280
      [&amp;lt;00000000313b1704&amp;gt;] binder_thread_write+0xdec/0x439c
      [&amp;lt;000000000cbd33bb&amp;gt;] binder_ioctl+0x1b68/0x22cc
      [&amp;lt;000000002bbedeeb&amp;gt;] __arm64_sys_ioctl+0x124/0x190
      [&amp;lt;00000000b439adee&amp;gt;] invoke_syscall+0x6c/0x254
      [&amp;lt;00000000173558fc&amp;gt;] el0_svc_common.constprop.0+0xac/0x230
      [&amp;lt;0000000084f72311&amp;gt;] do_el0_svc+0x40/0x58
      [&amp;lt;000000008b872457&amp;gt;] el0_svc+0x38/0x78
      [&amp;lt;00000000ee778653&amp;gt;] el0t_64_sync_handler+0x120/0x12c
      [&amp;lt;00000000a8ec61bf&amp;gt;] el0t_64_sync+0x190/0x194&lt;/p&gt;
&lt;p&gt;This patch fixes the leak by ensuring that any pending entries in
proc-&amp;gt;delivered_freeze are freed during binder_def…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2024-56553</guid>
    </item>
  </channel>
</rss>
