<?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 07:03:30 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2025-38175</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2025-38175</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:stream: linux-lts&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/bell-cve-2025-38175</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0828 — De multiples vulnérabilités ont été découvertes dans le noyau Linux d'Ubuntu. Certaines d'entre elles permettent à un a…</title>
      <link>https://127.0.0.1:10001/vuln/certfr-2025-avi-0828</link>
      <description>certfr-2025-avi-0828</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2025-avi-0828</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2025-38175</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2025-38175</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 83 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: binder: fix yet another UAF in binder_devices Commit e77aff5528a18 (&amp;#34;binderfs: fix use-after-free in binder_devices&amp;#34;) addressed a use-after-free where devices could be released without first being removed from the binder_devices list. However, there is a similar path in binder_free_proc() that was missed:   ==================================================================   BUG: KASAN: slab-use-after-free in binder_remove_device+0xd4/0x100   Write of size 8 at addr ffff0000c773b900 by task umount/467   CPU: 12 UID: 0 PID: 467 Comm: umount Not tainted 6.15.0-rc7-00138-g57483a362741 #9 PREEMPT   Hardware name: linux,dummy-virt (DT)   Call trace:    binder_remove_device+0xd4/0x100    binderfs_evict_inode+0x230/0x2f0    evict+0x25c/0x5dc    iput+0x304/0x480    dentry_unlink_inode+0x208/0x46c    __dentry_kill+0x154/0x530    [...]   Allocated by task 463:    __kmalloc_cache_noprof+0x13c/0x324    binderfs_binder_device_create.isra.0+0x138/0xa60    binder_ctl_ioctl+0x1ac/0x230   [...]   Freed by task 215:    kfree+0x184/0x31c    binder_proc_dec_tmpref+0x33c/0x4ac    binder_deferred_func+0xc10/0x1108    process_one_work+0x520/0xba4   [...]   ================================================================== Call binder_remove_device() within binder_free_proc() to ensure the device is removed from the binder_devices list before being kfreed.&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 83 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: binder: fix yet another UAF in binder_devices Commit e77aff5528a18 (&amp;#34;binderfs: fix use-after-free in binder_devices&amp;#34;) addressed a use-after-free where devices could be released without first being removed from the binder_devices list. However, there is a similar path in binder_free_proc() that was missed:   ==================================================================   BUG: KASAN: slab-use-after-free in binder_remove_device+0xd4/0x100   Write of size 8 at addr ffff0000c773b900 by task umount/467   CPU: 12 UID: 0 PID: 467 Comm: umount Not tainted 6.15.0-rc7-00138-g57483a362741 #9 PREEMPT   Hardware name: linux,dummy-virt (DT)   Call trace:    binder_remove_device+0xd4/0x100    binderfs_evict_inode+0x230/0x2f0    evict+0x25c/0x5dc    iput+0x304/0x480    dentry_unlink_inode+0x208/0x46c    __dentry_kill+0x154/0x530    [...]   Allocated by task 463:    __kmalloc_cache_noprof+0x13c/0x324    binderfs_binder_device_create.isra.0+0x138/0xa60    binder_ctl_ioctl+0x1ac/0x230   [...]   Freed by task 215:    kfree+0x184/0x31c    binder_proc_dec_tmpref+0x33c/0x4ac    binder_deferred_func+0xc10/0x1108    process_one_work+0x520/0xba4   [...]   ================================================================== Call binder_remove_device() within binder_free_proc() to ensure the device is removed from the binder_devices list before being kfreed.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2025-38175</guid>
    </item>
  </channel>
</rss>
