<?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 10:22:10 +0000</lastBuildDate>
    <item>
      <title>bdu:2025-07226</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2025-07226</link>
      <description>bdu:2025-07226</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2025-07226</guid>
    </item>
    <item>
      <title>BELL-CVE-2024-56554</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2024-56554</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-56554</guid>
    </item>
    <item>
      <title>EUVD-2026-346467</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-346467</link>
      <description>EUVD-2026-346467</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-346467</guid>
    </item>
    <item>
      <title>fkie_cve-2024-56554</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2024-56554</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;binder: fix freeze UAF in binder_release_work()&lt;/p&gt;
&lt;p&gt;When a binder reference is cleaned up, any freeze work queued in the
associated process should also be removed. Otherwise, the reference is
freed while its ref-&amp;gt;freeze.work is still queued in proc-&amp;gt;work leading
to a use-after-free issue as shown by the following KASAN report:&lt;/p&gt;
&lt;p&gt;==================================================================
  BUG: KASAN: slab-use-after-free in binder_release_work+0x398/0x3d0
  Read of size 8 at addr ffff31600ee91488 by task kworker/5:1/211&lt;/p&gt;
&lt;p&gt;CPU: 5 UID: 0 PID: 211 Comm: kworker/5:1 Not tainted 6.11.0-rc7-00382-gfc6c92196396 #22
  Hardware name: linux,dummy-virt (DT)
  Workqueue: events binder_deferred_func
  Call trace:
   binder_release_work+0x398/0x3d0
   binder_deferred_func+0xb60/0x109c
   process_one_work+0x51c/0xbd4
   worker_thread+0x608/0xee8&lt;/p&gt;
&lt;p&gt;Allocated by task 703:
   __kmalloc_cache_noprof+0x130/0x280
   binder_thread_write+0xdb4/0x42a0
   binder_ioctl+0x18f0/0x25ac
   __arm64_sys_ioctl+0x124/0x190
   invoke_syscall+0x6c/0x254&lt;/p&gt;
&lt;p&gt;Freed by task 211:
   kfree+0xc4/0x230
   binder_deferred_func+0xae8/0x109c
   process_one_work+0x51c/0xbd4
   worker_thread+0x608/0xee8
  ==================================================================&lt;/p&gt;
&lt;p&gt;This commit fixes the issue by ensuring any queued freeze work is removed
when cleaning up a binder reference.&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 freeze UAF in binder_release_work()&lt;/p&gt;
&lt;p&gt;When a binder reference is cleaned up, any freeze work queued in the
associated process should also be removed. Otherwise, the reference is
freed while its ref-&amp;gt;freeze.work is still queued in proc-&amp;gt;work leading
to a use-after-free issue as shown by the following KASAN report:&lt;/p&gt;
&lt;p&gt;==================================================================
  BUG: KASAN: slab-use-after-free in binder_release_work+0x398/0x3d0
  Read of size 8 at addr ffff31600ee91488 by task kworker/5:1/211&lt;/p&gt;
&lt;p&gt;CPU: 5 UID: 0 PID: 211 Comm: kworker/5:1 Not tainted 6.11.0-rc7-00382-gfc6c92196396 #22
  Hardware name: linux,dummy-virt (DT)
  Workqueue: events binder_deferred_func
  Call trace:
   binder_release_work+0x398/0x3d0
   binder_deferred_func+0xb60/0x109c
   process_one_work+0x51c/0xbd4
   worker_thread+0x608/0xee8&lt;/p&gt;
&lt;p&gt;Allocated by task 703:
   __kmalloc_cache_noprof+0x130/0x280
   binder_thread_write+0xdb4/0x42a0
   binder_ioctl+0x18f0/0x25ac
   __arm64_sys_ioctl+0x124/0x190
   invoke_syscall+0x6c/0x254&lt;/p&gt;
&lt;p&gt;Freed by task 211:
   kfree+0xc4/0x230
   binder_deferred_func+0xae8/0x109c
   process_one_work+0x51c/0xbd4
   worker_thread+0x608/0xee8
  ==================================================================&lt;/p&gt;
&lt;p&gt;This commit fixes the issue by ensuring any queued freeze work is removed
when cleaning up a binder reference.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2024-56554</guid>
    </item>
    <item>
      <title>GHSA-983j-f2fq-2775</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-983j-f2fq-2775</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;binder: fix freeze UAF in binder_release_work()&lt;/p&gt;
&lt;p&gt;When a binder reference is cleaned up, any freeze work queued in the
associated process should also be removed. Otherwise, the reference is
freed while its ref-&amp;gt;freeze.work is still queued in proc-&amp;gt;work leading
to a use-after-free issue as shown by the following KASAN report:&lt;/p&gt;
&lt;p&gt;==================================================================
  BUG: KASAN: slab-use-after-free in binder_release_work+0x398/0x3d0
  Read of size 8 at addr ffff31600ee91488 by task kworker/5:1/211&lt;/p&gt;
&lt;p&gt;CPU: 5 UID: 0 PID: 211 Comm: kworker/5:1 Not tainted 6.11.0-rc7-00382-gfc6c92196396 #22
  Hardware name: linux,dummy-virt (DT)
  Workqueue: events binder_deferred_func
  Call trace:
   binder_release_work+0x398/0x3d0
   binder_deferred_func+0xb60/0x109c
   process_one_work+0x51c/0xbd4
   worker_thread+0x608/0xee8&lt;/p&gt;
&lt;p&gt;Allocated by task 703:
   __kmalloc_cache_noprof+0x130/0x280
   binder_thread_write+0xdb4/0x42a0
   binder_ioctl+0x18f0/0x25ac
   __arm64_sys_ioctl+0x124/0x190
   invoke_syscall+0x6c/0x254&lt;/p&gt;
&lt;p&gt;Freed by task 211:
   kfree+0xc4/0x230
   binder_deferred_func+0xae8/0x109c
   process_one_work+0x51c/0xbd4
   worker_thread+0x608/0xee8
  ==================================================================&lt;/p&gt;
&lt;p&gt;This commit fixes the issue by ensuring any queued freeze work is removed
when cleaning up a binder reference.&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 freeze UAF in binder_release_work()&lt;/p&gt;
&lt;p&gt;When a binder reference is cleaned up, any freeze work queued in the
associated process should also be removed. Otherwise, the reference is
freed while its ref-&amp;gt;freeze.work is still queued in proc-&amp;gt;work leading
to a use-after-free issue as shown by the following KASAN report:&lt;/p&gt;
&lt;p&gt;==================================================================
  BUG: KASAN: slab-use-after-free in binder_release_work+0x398/0x3d0
  Read of size 8 at addr ffff31600ee91488 by task kworker/5:1/211&lt;/p&gt;
&lt;p&gt;CPU: 5 UID: 0 PID: 211 Comm: kworker/5:1 Not tainted 6.11.0-rc7-00382-gfc6c92196396 #22
  Hardware name: linux,dummy-virt (DT)
  Workqueue: events binder_deferred_func
  Call trace:
   binder_release_work+0x398/0x3d0
   binder_deferred_func+0xb60/0x109c
   process_one_work+0x51c/0xbd4
   worker_thread+0x608/0xee8&lt;/p&gt;
&lt;p&gt;Allocated by task 703:
   __kmalloc_cache_noprof+0x130/0x280
   binder_thread_write+0xdb4/0x42a0
   binder_ioctl+0x18f0/0x25ac
   __arm64_sys_ioctl+0x124/0x190
   invoke_syscall+0x6c/0x254&lt;/p&gt;
&lt;p&gt;Freed by task 211:
   kfree+0xc4/0x230
   binder_deferred_func+0xae8/0x109c
   process_one_work+0x51c/0xbd4
   worker_thread+0x608/0xee8
  ==================================================================&lt;/p&gt;
&lt;p&gt;This commit fixes the issue by ensuring any queued freeze work is removed
when cleaning up a binder reference.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-983j-f2fq-2775</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2024-56554</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-56554</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 freeze UAF in binder_release_work() When a binder reference is cleaned up, any freeze work queued in the associated process should also be removed. Otherwise, the reference is freed while its ref-&amp;gt;freeze.work is still queued in proc-&amp;gt;work leading to a use-after-free issue as shown by the following KASAN report:   ==================================================================   BUG: KASAN: slab-use-after-free in binder_release_work+0x398/0x3d0   Read of size 8 at addr ffff31600ee91488 by task kworker/5:1/211   CPU: 5 UID: 0 PID: 211 Comm: kworker/5:1 Not tainted 6.11.0-rc7-00382-gfc6c92196396 #22   Hardware name: linux,dummy-virt (DT)   Workqueue: events binder_deferred_func   Call trace:    binder_release_work+0x398/0x3d0    binder_deferred_func+0xb60/0x109c    process_one_work+0x51c/0xbd4    worker_thread+0x608/0xee8   Allocated by task 703:    __kmalloc_cache_noprof+0x130/0x280    binder_thread_write+0xdb4/0x42a0    binder_ioctl+0x18f0/0x25ac    __arm64_sys_ioctl+0x124/0x190    invoke_syscall+0x6c/0x254   Freed by task 211:    kfree+0xc4/0x230    binder_deferred_func+0xae8/0x109c    process_one_work+0x51c/0xbd4    worker_thread+0x608/0xee8   ================================================================== This commit fixes the issue by ensuring any queued freeze work is removed when cleaning up a binder reference.&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 freeze UAF in binder_release_work() When a binder reference is cleaned up, any freeze work queued in the associated process should also be removed. Otherwise, the reference is freed while its ref-&amp;gt;freeze.work is still queued in proc-&amp;gt;work leading to a use-after-free issue as shown by the following KASAN report:   ==================================================================   BUG: KASAN: slab-use-after-free in binder_release_work+0x398/0x3d0   Read of size 8 at addr ffff31600ee91488 by task kworker/5:1/211   CPU: 5 UID: 0 PID: 211 Comm: kworker/5:1 Not tainted 6.11.0-rc7-00382-gfc6c92196396 #22   Hardware name: linux,dummy-virt (DT)   Workqueue: events binder_deferred_func   Call trace:    binder_release_work+0x398/0x3d0    binder_deferred_func+0xb60/0x109c    process_one_work+0x51c/0xbd4    worker_thread+0x608/0xee8   Allocated by task 703:    __kmalloc_cache_noprof+0x130/0x280    binder_thread_write+0xdb4/0x42a0    binder_ioctl+0x18f0/0x25ac    __arm64_sys_ioctl+0x124/0x190    invoke_syscall+0x6c/0x254   Freed by task 211:    kfree+0xc4/0x230    binder_deferred_func+0xae8/0x109c    process_one_work+0x51c/0xbd4    worker_thread+0x608/0xee8   ================================================================== This commit fixes the issue by ensuring any queued freeze work is removed when cleaning up a binder reference.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-56554</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>
