<?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 21:35:26 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-56556 — binder: fix node UAF in binder_add_freeze_work()</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2024-56556</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 node UAF in binder_add_freeze_work()&lt;/p&gt;
&lt;p&gt;In binder_add_freeze_work() we iterate over the proc-&amp;gt;nodes with the
proc-&amp;gt;inner_lock held. However, this lock is temporarily dropped in
order to acquire the node-&amp;gt;lock first (lock nesting order). This can
race with binder_node_release() and trigger a use-after-free:&lt;/p&gt;
&lt;p&gt;==================================================================
  BUG: KASAN: slab-use-after-free in _raw_spin_lock+0xe4/0x19c
  Write of size 4 at addr ffff53c04c29dd04 by task freeze/640&lt;/p&gt;
&lt;p&gt;CPU: 5 UID: 0 PID: 640 Comm: freeze Not tainted 6.11.0-07343-ga727812a8d45 #17
  Hardware name: linux,dummy-virt (DT)
  Call trace:
   _raw_spin_lock+0xe4/0x19c
   binder_add_freeze_work+0x148/0x478
   binder_ioctl+0x1e70/0x25ac
   __arm64_sys_ioctl+0x124/0x190&lt;/p&gt;
&lt;p&gt;Allocated by task 637:
   __kmalloc_cache_noprof+0x12c/0x27c
   binder_new_node+0x50/0x700
   binder_transaction+0x35ac/0x6f74
   binder_thread_write+0xfb8/0x42a0
   binder_ioctl+0x18f0/0x25ac
   __arm64_sys_ioctl+0x124/0x190&lt;/p&gt;
&lt;p&gt;Freed by task 637:
   kfree+0xf0/0x330
   binder_thread_read+0x1e88/0x3a68
   binder_ioctl+0x16d8/0x25ac
   __arm64_sys_ioctl+0x124/0x190
  ==================================================================&lt;/p&gt;
&lt;p&gt;Fix the race by taking a temporary reference on the node before
releasing the proc-&amp;gt;inner lock. This ensures the node remains alive
while in use.&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 node UAF in binder_add_freeze_work()&lt;/p&gt;
&lt;p&gt;In binder_add_freeze_work() we iterate over the proc-&amp;gt;nodes with the
proc-&amp;gt;inner_lock held. However, this lock is temporarily dropped in
order to acquire the node-&amp;gt;lock first (lock nesting order). This can
race with binder_node_release() and trigger a use-after-free:&lt;/p&gt;
&lt;p&gt;==================================================================
  BUG: KASAN: slab-use-after-free in _raw_spin_lock+0xe4/0x19c
  Write of size 4 at addr ffff53c04c29dd04 by task freeze/640&lt;/p&gt;
&lt;p&gt;CPU: 5 UID: 0 PID: 640 Comm: freeze Not tainted 6.11.0-07343-ga727812a8d45 #17
  Hardware name: linux,dummy-virt (DT)
  Call trace:
   _raw_spin_lock+0xe4/0x19c
   binder_add_freeze_work+0x148/0x478
   binder_ioctl+0x1e70/0x25ac
   __arm64_sys_ioctl+0x124/0x190&lt;/p&gt;
&lt;p&gt;Allocated by task 637:
   __kmalloc_cache_noprof+0x12c/0x27c
   binder_new_node+0x50/0x700
   binder_transaction+0x35ac/0x6f74
   binder_thread_write+0xfb8/0x42a0
   binder_ioctl+0x18f0/0x25ac
   __arm64_sys_ioctl+0x124/0x190&lt;/p&gt;
&lt;p&gt;Freed by task 637:
   kfree+0xf0/0x330
   binder_thread_read+0x1e88/0x3a68
   binder_ioctl+0x16d8/0x25ac
   __arm64_sys_ioctl+0x124/0x190
  ==================================================================&lt;/p&gt;
&lt;p&gt;Fix the race by taking a temporary reference on the node before
releasing the proc-&amp;gt;inner lock. This ensures the node remains alive
while in use.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2024-56556</guid>
    </item>
  </channel>
</rss>
