<?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:49 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-64468</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2026-64468</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-64468</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-64468</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2026-64468</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 237 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: binder: fix UAF in binder_free_transaction() In binder_free_transaction(), the t-&amp;gt;to_proc is read under the t-&amp;gt;lock. However, once the t-&amp;gt;lock is dropped, the to_proc can die in parallel. This leads to a use-after-free error when we attempt to acquire its inner lock right afterwards:   ==================================================================   BUG: KASAN: slab-use-after-free in _raw_spin_lock+0xe4/0x1a0   Write of size 4 at addr ffff00001125da70 by task B/672   CPU: 20 UID: 0 PID: 672 Comm: B Not tainted 7.1.0-rc6-00284-g8e65320d91cd #4 PREEMPT   Hardware name: linux,dummy-virt (DT)   Call trace:    _raw_spin_lock+0xe4/0x1a0    binder_free_transaction+0x8c/0x320    binder_send_failed_reply+0x21c/0x2f8    binder_thread_release+0x488/0x7e0    binder_ioctl+0x12c0/0x29a0   [...]   Allocated by task 675:    __kmalloc_cache_noprof+0x174/0x444    binder_open+0x118/0xb70    do_dentry_open+0x374/0x1040    vfs_open+0x58/0x3bc   [...]   Freed by task 212:    __kasan_slab_free+0x58/0x80    kfree+0x1a0/0x4a4    binder_proc_dec_tmpref+0x32c/0x5e0    binder_deferred_func+0xc48/0x104c    process_one_work+0x53c/0xbc0   [...]   ================================================================== To prevent this, pin the target thread (t-&amp;gt;to_thread) to guarantee the target process remains alive. Undelivered transactions without a target thread are already safe, as the target process can only be the current context in t…&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 237 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: binder: fix UAF in binder_free_transaction() In binder_free_transaction(), the t-&amp;gt;to_proc is read under the t-&amp;gt;lock. However, once the t-&amp;gt;lock is dropped, the to_proc can die in parallel. This leads to a use-after-free error when we attempt to acquire its inner lock right afterwards:   ==================================================================   BUG: KASAN: slab-use-after-free in _raw_spin_lock+0xe4/0x1a0   Write of size 4 at addr ffff00001125da70 by task B/672   CPU: 20 UID: 0 PID: 672 Comm: B Not tainted 7.1.0-rc6-00284-g8e65320d91cd #4 PREEMPT   Hardware name: linux,dummy-virt (DT)   Call trace:    _raw_spin_lock+0xe4/0x1a0    binder_free_transaction+0x8c/0x320    binder_send_failed_reply+0x21c/0x2f8    binder_thread_release+0x488/0x7e0    binder_ioctl+0x12c0/0x29a0   [...]   Allocated by task 675:    __kmalloc_cache_noprof+0x174/0x444    binder_open+0x118/0xb70    do_dentry_open+0x374/0x1040    vfs_open+0x58/0x3bc   [...]   Freed by task 212:    __kasan_slab_free+0x58/0x80    kfree+0x1a0/0x4a4    binder_proc_dec_tmpref+0x32c/0x5e0    binder_deferred_func+0xc48/0x104c    process_one_work+0x53c/0xbc0   [...]   ================================================================== To prevent this, pin the target thread (t-&amp;gt;to_thread) to guarantee the target process remains alive. Undelivered transactions without a target thread are already safe, as the target process can only be the current context in t…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2026-64468</guid>
    </item>
  </channel>
</rss>
