<?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://127.0.0.1:10001</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>Sat, 21 Nov 2026 06:03:51 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-64469</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2026-64469</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, 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:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/bell-cve-2026-64469</guid>
    </item>
    <item>
      <title>certfr-2026-avi-0982 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian LTS. Elles permettent à un attaquant de p…</title>
      <link>https://127.0.0.1:10001/vuln/certfr-2026-avi-0982</link>
      <description>certfr-2026-avi-0982</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2026-avi-0982</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-64469</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2026-64469</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe, Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:Pro:16.04:LTS: linux-oracle, Ubuntu:Pro:18.04:LTS: linux, Ubuntu:Pro:18.04:LTS: linux-aws, Ubuntu:18.04:LTS: linux-aws-5.0 and 240 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: binder: fix UAF in binder_thread_release() When a thread exits, binder_thread_release() walks its transaction stack to clear the t-&amp;gt;from and t-&amp;gt;to_proc that correspond with the exiting thread. However, a process dying in parallel might attempt to kfree some of these transactions. And if one of them has no associated t-&amp;gt;to_proc, the t-&amp;gt;to_proc-&amp;gt;inner_lock will not be acquired. This means that transaction accesses in binder_thread_release() after t-&amp;gt;to_proc has been cleared might race with binder_free_transaction() and cause a use-after-free error as reported by KASAN:   ==================================================================   BUG: KASAN: slab-use-after-free in binder_thread_release+0x5d0/0x798   Write of size 8 at addr ffff000016627500 by task X/715   CPU: 17 UID: 0 PID: 715 Comm: X Not tainted 7.1.0-rc5-00149-g8fde5d1d47f6 #30 PREEMPT   Hardware name: linux,dummy-virt (DT)   Call trace:    binder_thread_release+0x5d0/0x798    binder_ioctl+0x12c0/0x299c    [...]   Allocated by task 717 on cpu 18 at 67.267803s:    __kasan_kmalloc+0xa0/0xbc    __kmalloc_cache_noprof+0x174/0x444    binder_transaction+0x554/0x8150    binder_thread_write+0xa30/0x4354    binder_ioctl+0x20f0/0x299c    [...]   Freed by task 202 on cpu 18 at 90.416221s:    __kasan_slab_free+0x58/0x80    kfree+0x1a0/0x4a4    binder_free_transaction+0x150/0x294    binder_send_failed_reply+0x398/0x6d8    binder_release_work+0x3e4/0x4ec    bin…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe, Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:Pro:16.04:LTS: linux-oracle, Ubuntu:Pro:18.04:LTS: linux, Ubuntu:Pro:18.04:LTS: linux-aws, Ubuntu:18.04:LTS: linux-aws-5.0 and 240 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: binder: fix UAF in binder_thread_release() When a thread exits, binder_thread_release() walks its transaction stack to clear the t-&amp;gt;from and t-&amp;gt;to_proc that correspond with the exiting thread. However, a process dying in parallel might attempt to kfree some of these transactions. And if one of them has no associated t-&amp;gt;to_proc, the t-&amp;gt;to_proc-&amp;gt;inner_lock will not be acquired. This means that transaction accesses in binder_thread_release() after t-&amp;gt;to_proc has been cleared might race with binder_free_transaction() and cause a use-after-free error as reported by KASAN:   ==================================================================   BUG: KASAN: slab-use-after-free in binder_thread_release+0x5d0/0x798   Write of size 8 at addr ffff000016627500 by task X/715   CPU: 17 UID: 0 PID: 715 Comm: X Not tainted 7.1.0-rc5-00149-g8fde5d1d47f6 #30 PREEMPT   Hardware name: linux,dummy-virt (DT)   Call trace:    binder_thread_release+0x5d0/0x798    binder_ioctl+0x12c0/0x299c    [...]   Allocated by task 717 on cpu 18 at 67.267803s:    __kasan_kmalloc+0xa0/0xbc    __kmalloc_cache_noprof+0x174/0x444    binder_transaction+0x554/0x8150    binder_thread_write+0xa30/0x4354    binder_ioctl+0x20f0/0x299c    [...]   Freed by task 202 on cpu 18 at 90.416221s:    __kasan_slab_free+0x58/0x80    kfree+0x1a0/0x4a4    binder_free_transaction+0x150/0x294    binder_send_failed_reply+0x398/0x6d8    binder_release_work+0x3e4/0x4ec    bin…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2026-64469</guid>
    </item>
  </channel>
</rss>
