<?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:09:37 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-98735</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2026-98735</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-98735</guid>
    </item>
    <item>
      <title>certfr-2026-avi-1375 — 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-1375</link>
      <description>certfr-2026-avi-1375</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2026-avi-1375</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-98735</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2026-98735</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux, 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 and 248 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: Bluetooth: hci_core: Serialize ACL scheduling with channel deletion hci_chan_sent() selects a channel under RCU but drops the read lock before accessing chan-&amp;gt;conn and returning the channel. The ACL and LE schedulers then use its packet queue and update its transmit counters without any protection against channel deletion. After TX selects a channel and releases RCU, a disconnect command timeout on the separate request workqueue can run hci_conn_failed() and l2cap_conn_del(). hci_chan_del() can then unlink the channel, complete synchronize_rcu(), purge its queue and free it before TX resumes. This causes use-after-free both in hci_chan_sent() and in its callers. KASAN reported:   BUG: KASAN: slab-use-after-free in hci_chan_sent+0x892/0x9b0   Workqueue: hci0 hci_tx_work   Call Trace:    hci_chan_sent+0x892/0x9b0    hci_tx_work+0x5e6/0xb70   Allocated by task 91:    hci_chan_create+0xe3/0x350    l2cap_conn_add.part.0+0x12/0xa30    l2cap_chan_connect+0x110d/0x1b60    l2cap_sock_connect+0x310/0x530   Freed by task 99:    hci_chan_del+0x11f/0x170    l2cap_conn_del+0x4f1/0x800    l2cap_connect_cfm+0x88c/0xd30    hci_conn_failed+0x150/0x250    hci_abort_conn_sync+0x3e3/0x800    hci_cmd_sync_run+0x7e/0xc0    hci_abort_conn+0x105/0x1f0    disconnect_sync+0x157/0x290    hci_cmd_sync_work+0x13c/0x290 Hold the existing device mutex across channel selection and transmission in both schedulers to serialize them with chann…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux, 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 and 248 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: Bluetooth: hci_core: Serialize ACL scheduling with channel deletion hci_chan_sent() selects a channel under RCU but drops the read lock before accessing chan-&amp;gt;conn and returning the channel. The ACL and LE schedulers then use its packet queue and update its transmit counters without any protection against channel deletion. After TX selects a channel and releases RCU, a disconnect command timeout on the separate request workqueue can run hci_conn_failed() and l2cap_conn_del(). hci_chan_del() can then unlink the channel, complete synchronize_rcu(), purge its queue and free it before TX resumes. This causes use-after-free both in hci_chan_sent() and in its callers. KASAN reported:   BUG: KASAN: slab-use-after-free in hci_chan_sent+0x892/0x9b0   Workqueue: hci0 hci_tx_work   Call Trace:    hci_chan_sent+0x892/0x9b0    hci_tx_work+0x5e6/0xb70   Allocated by task 91:    hci_chan_create+0xe3/0x350    l2cap_conn_add.part.0+0x12/0xa30    l2cap_chan_connect+0x110d/0x1b60    l2cap_sock_connect+0x310/0x530   Freed by task 99:    hci_chan_del+0x11f/0x170    l2cap_conn_del+0x4f1/0x800    l2cap_connect_cfm+0x88c/0xd30    hci_conn_failed+0x150/0x250    hci_abort_conn_sync+0x3e3/0x800    hci_cmd_sync_run+0x7e/0xc0    hci_abort_conn+0x105/0x1f0    disconnect_sync+0x157/0x290    hci_cmd_sync_work+0x13c/0x290 Hold the existing device mutex across channel selection and transmission in both schedulers to serialize them with chann…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2026-98735</guid>
    </item>
  </channel>
</rss>
