<?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 16:35:39 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-80762</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2026-80762</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-80762</guid>
    </item>
    <item>
      <title>certfr-2026-avi-1163 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian LTS. Certaines d'entre elles permettent à…</title>
      <link>https://127.0.0.1:10001/vuln/certfr-2026-avi-1163</link>
      <description>certfr-2026-avi-1163</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2026-avi-1163</guid>
    </item>
    <item>
      <title>OESA-2026-4358 — kernel security update</title>
      <link>https://127.0.0.1:10001/vuln/oesa-2026-4358</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:24.03-LTS-SP1: kernel&lt;/p&gt;
&lt;p&gt;The Linux Kernel, the operating system core itself.&#13;
&#13;
Security Fix(es):&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;erofs: fix inline data read failure for ztailpacking pclusters&lt;/p&gt;
&lt;p&gt;Compressed folios for ztailpacking pclusters must be valid before adding
these pclusters to I/O chains. Otherwise, z_erofs_decompress_pcluster()
may assume they are already valid and then trigger a NULL pointer
dereference.&lt;/p&gt;
&lt;p&gt;It is somewhat hard to reproduce because the inline data is in the same
block as the tail of the compressed indexes, which are usually read just
before. However, it may still happen if a fatal signal arrives while
read_mapping_folio() is running, as shown below:&lt;/p&gt;
&lt;p&gt;erofs: (device dm-1): z_erofs_pcluster_begin: failed to get inline data -4
 Unable to handle kernel NULL pointer dereference at virtual address 0000000000000008&lt;/p&gt;
&lt;p&gt;...&lt;/p&gt;
&lt;p&gt;pc : z_erofs_decompress_queue+0x4c8/0xa14
 lr : z_erofs_decompress_queue+0x160/0xa14
 sp : ffffffc08b3eb3a0
 x29: ffffffc08b3eb570 x28: ffffffc08b3eb418 x27: 0000000000001000
 x26: ffffff8086ebdbb8 x25: ffffff8086ebdbb8 x24: 0000000000000001
 x23: 0000000000000008 x22: 00000000fffffffb x21: dead000000000700
 x20: 00000000000015e7 x19: ffffff808babb400 x18: ffffffc089edc098
 x17: 00000000c006287d x16: 00000000c006287d x15: 0000000000000004
 x14: ffffff80ba8f8000 x13: 0000000000000004 x12: 00000006589a77c9
 x11: 0000000000000015 x10: 0000000000000000 x9 : 0000000000000000
 x8 : 0000000000000000 x7 : 0000000000000000 x6 : 000000…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:24.03-LTS-SP1: kernel&lt;/p&gt;
&lt;p&gt;The Linux Kernel, the operating system core itself.&#13;
&#13;
Security Fix(es):&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;erofs: fix inline data read failure for ztailpacking pclusters&lt;/p&gt;
&lt;p&gt;Compressed folios for ztailpacking pclusters must be valid before adding
these pclusters to I/O chains. Otherwise, z_erofs_decompress_pcluster()
may assume they are already valid and then trigger a NULL pointer
dereference.&lt;/p&gt;
&lt;p&gt;It is somewhat hard to reproduce because the inline data is in the same
block as the tail of the compressed indexes, which are usually read just
before. However, it may still happen if a fatal signal arrives while
read_mapping_folio() is running, as shown below:&lt;/p&gt;
&lt;p&gt;erofs: (device dm-1): z_erofs_pcluster_begin: failed to get inline data -4
 Unable to handle kernel NULL pointer dereference at virtual address 0000000000000008&lt;/p&gt;
&lt;p&gt;...&lt;/p&gt;
&lt;p&gt;pc : z_erofs_decompress_queue+0x4c8/0xa14
 lr : z_erofs_decompress_queue+0x160/0xa14
 sp : ffffffc08b3eb3a0
 x29: ffffffc08b3eb570 x28: ffffffc08b3eb418 x27: 0000000000001000
 x26: ffffff8086ebdbb8 x25: ffffff8086ebdbb8 x24: 0000000000000001
 x23: 0000000000000008 x22: 00000000fffffffb x21: dead000000000700
 x20: 00000000000015e7 x19: ffffff808babb400 x18: ffffffc089edc098
 x17: 00000000c006287d x16: 00000000c006287d x15: 0000000000000004
 x14: ffffff80ba8f8000 x13: 0000000000000004 x12: 00000006589a77c9
 x11: 0000000000000015 x10: 0000000000000000 x9 : 0000000000000000
 x8 : 0000000000000000 x7 : 0000000000000000 x6 : 000000…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/oesa-2026-4358</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-80762</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2026-80762</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 155 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: Bluetooth: hci_sync: Fix accept list UAF during suspend hci_update_event_filter_sync() walks hdev-&amp;gt;accept_list while sending a synchronous HCI command for each remote-wakeup device.  The suspend path holds hdev-&amp;gt;req_lock, but accept-list updates are serialized by hdev-&amp;gt;lock. Consequently, remove_device() can free the current list entry during the controller wait. The following interleaving causes the use-after-free:   hci_update_event_filter_sync()    remove_device()   fetch accept-list entry   hci_set_event_filter_sync()     wait for controller response    hci_dev_lock()                                     list_del()                                     kfree()                                     hci_dev_unlock()   read the freed list.next KASAN reported:   BUG: KASAN: slab-use-after-free in hci_suspend_sync+0x835/0x910   Read of size 8 at addr ffff88810bec8440 by task kworker/0:1/10   Workqueue: events vhci_suspend_work   Call Trace:    hci_suspend_sync+0x835/0x910    hci_suspend_dev+0x182/0x450    process_one_work+0x661/0x1090    worker_thread+0x45b/0xd10   Allocated by task 86:    hci_bdaddr_list_add_with_flags+0x1a8/0x400    add_device+0x381/0x820    hci_sock_sendmsg+0x1033/0x1ea0   Freed by task 91:    kfree+0x131/0x3c0    remove_device+0x429/0xb70    hci_sock_sendmsg+0x1033/0x1ea0 Snapshot the remote-wakeup addresses under hdev-&amp;gt;lock.  Release the lock before sending HCI commands.  Clear the controller…&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 155 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: Bluetooth: hci_sync: Fix accept list UAF during suspend hci_update_event_filter_sync() walks hdev-&amp;gt;accept_list while sending a synchronous HCI command for each remote-wakeup device.  The suspend path holds hdev-&amp;gt;req_lock, but accept-list updates are serialized by hdev-&amp;gt;lock. Consequently, remove_device() can free the current list entry during the controller wait. The following interleaving causes the use-after-free:   hci_update_event_filter_sync()    remove_device()   fetch accept-list entry   hci_set_event_filter_sync()     wait for controller response    hci_dev_lock()                                     list_del()                                     kfree()                                     hci_dev_unlock()   read the freed list.next KASAN reported:   BUG: KASAN: slab-use-after-free in hci_suspend_sync+0x835/0x910   Read of size 8 at addr ffff88810bec8440 by task kworker/0:1/10   Workqueue: events vhci_suspend_work   Call Trace:    hci_suspend_sync+0x835/0x910    hci_suspend_dev+0x182/0x450    process_one_work+0x661/0x1090    worker_thread+0x45b/0xd10   Allocated by task 86:    hci_bdaddr_list_add_with_flags+0x1a8/0x400    add_device+0x381/0x820    hci_sock_sendmsg+0x1033/0x1ea0   Freed by task 91:    kfree+0x131/0x3c0    remove_device+0x429/0xb70    hci_sock_sendmsg+0x1033/0x1ea0 Snapshot the remote-wakeup addresses under hdev-&amp;gt;lock.  Release the lock before sending HCI commands.  Clear the controller…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2026-80762</guid>
    </item>
  </channel>
</rss>
