<?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 05:59:27 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-64455</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2026-64455</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-64455</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-64455</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2026-64455</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, 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 and 247 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: USB: chaoskey: Fix slab-use-after-free in chaoskey_release() The chaoskey driver has a use-after-free bug in its release routine. If the user closes the device file after the USB device has been unplugged, a debugging log statement will try to access the usb_interface structure after it has been deallocated: 	BUG: KASAN: slab-use-after-free in dev_driver_string (drivers/base/core.c:2406) 	Read of size 8 at addr ffff888168e8a0b8 by task chaoskey_raw_re/10106 	Hardware name: QEMU Ubuntu 24.04 PC v2 (i440FX + PIIX, arch_caps fix, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 	Call Trace: 	 &amp;lt;TASK&amp;gt; 	 dump_stack_lvl (lib/dump_stack.c:94 lib/dump_stack.c:120) 	 print_report (mm/kasan/report.c:378 mm/kasan/report.c:482) 	 kasan_report (mm/kasan/report.c:595) 	 dev_driver_string (drivers/base/core.c:2406) 	 __dynamic_dev_dbg (lib/dynamic_debug.c:906) 	 chaoskey_release (drivers/usb/misc/chaoskey.c:323) 	 __fput (fs/file_table.c:510) 	 fput_close_sync (fs/file_table.c:615) 	 __x64_sys_close (fs/open.c:1507 fs/open.c:1492 fs/open.c:1492) 	 do_syscall_64 (arch/x86/entry/syscall_64.c:63 arch/x86/entry/syscall_64.c:94) 	 entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:121) The driver&amp;#39;s last reference to the interface structure is dropped in the chaoskey_free() routine, so the code must not use the interface -- even in a debugging statement -- after that routine returns. (Exception: If we know that another refere…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, 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 and 247 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: USB: chaoskey: Fix slab-use-after-free in chaoskey_release() The chaoskey driver has a use-after-free bug in its release routine. If the user closes the device file after the USB device has been unplugged, a debugging log statement will try to access the usb_interface structure after it has been deallocated: 	BUG: KASAN: slab-use-after-free in dev_driver_string (drivers/base/core.c:2406) 	Read of size 8 at addr ffff888168e8a0b8 by task chaoskey_raw_re/10106 	Hardware name: QEMU Ubuntu 24.04 PC v2 (i440FX + PIIX, arch_caps fix, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 	Call Trace: 	 &amp;lt;TASK&amp;gt; 	 dump_stack_lvl (lib/dump_stack.c:94 lib/dump_stack.c:120) 	 print_report (mm/kasan/report.c:378 mm/kasan/report.c:482) 	 kasan_report (mm/kasan/report.c:595) 	 dev_driver_string (drivers/base/core.c:2406) 	 __dynamic_dev_dbg (lib/dynamic_debug.c:906) 	 chaoskey_release (drivers/usb/misc/chaoskey.c:323) 	 __fput (fs/file_table.c:510) 	 fput_close_sync (fs/file_table.c:615) 	 __x64_sys_close (fs/open.c:1507 fs/open.c:1492 fs/open.c:1492) 	 do_syscall_64 (arch/x86/entry/syscall_64.c:63 arch/x86/entry/syscall_64.c:94) 	 entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:121) The driver&amp;#39;s last reference to the interface structure is dropped in the chaoskey_free() routine, so the code must not use the interface -- even in a debugging statement -- after that routine returns. (Exception: If we know that another refere…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2026-64455</guid>
    </item>
  </channel>
</rss>
