<?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://cve.radiocsirt.org</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>Sun, 04 Oct 2026 12:12:41 +0000</lastBuildDate>
    <item>
      <title>bdu:2025-15878</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2025-15878</link>
      <description>bdu:2025-15878</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2025-15878</guid>
    </item>
    <item>
      <title>BELL-CVE-2024-56553</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2024-56553</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2024-56553</guid>
    </item>
    <item>
      <title>EUVD-2026-313718</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-313718</link>
      <description>EUVD-2026-313718</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-313718</guid>
    </item>
    <item>
      <title>fkie_cve-2024-56553</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2024-56553</link>
      <description>&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;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://cve.radiocsirt.org/vuln/fkie_cve-2024-56553</guid>
    </item>
    <item>
      <title>GHSA-qvfp-2hw2-qffh</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-qvfp-2hw2-qffh</link>
      <description>&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;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://cve.radiocsirt.org/vuln/ghsa-qvfp-2hw2-qffh</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2024-56553</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-56553</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 69 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: binder: fix memleak of proc-&amp;gt;delivered_freeze 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:   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 This patch fixes the leak by ensuring that any pending entries in proc-&amp;gt;delivered_freeze are freed during binder_deferre…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 69 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: binder: fix memleak of proc-&amp;gt;delivered_freeze 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:   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 This patch fixes the leak by ensuring that any pending entries in proc-&amp;gt;delivered_freeze are freed during binder_deferre…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-56553</guid>
    </item>
    <item>
      <title>WID-SEC-W-2024-3762 — Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2024-3762</link>
      <description>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen und um nicht näher beschriebene Effekte zu erzielen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen und um nicht näher beschriebene Effekte zu erzielen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2024-3762</guid>
    </item>
  </channel>
</rss>
