<?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 08:56:42 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-99012</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2026-99012</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-99012</guid>
    </item>
    <item>
      <title>certfr-2026-avi-1470 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de SUSE. Certaines d'entre elles permettent à un at…</title>
      <link>https://127.0.0.1:10001/vuln/certfr-2026-avi-1470</link>
      <description>certfr-2026-avi-1470</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2026-avi-1470</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-99012</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2026-99012</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 164 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: Bluetooth: ISO: Serialize concurrent connect calls iso_sock_connect() checks the socket state before taking the socket lock and drops the lock again before setting up a connection. Two callers can both pass the admission check while the socket is open or bound. Caller A can copy its destination for route selection, then caller B can replace the socket destination before A binds or connects the CIS. A then uses B&amp;#39;s destination with the route selected for its own request. B can also proceed after A attaches a connection and sets BT_CONNECT. For deferred BIS setup, B can bind a second BIS and overwrite iso_pi(sk)-&amp;gt;conn, leaving the first connection&amp;#39;s reference and conn-&amp;gt;sk back-pointer stranded. Concurrent CIS connects can likewise replace the socket&amp;#39;s connection. Later teardown only detaches the current connection, so a callback on the old connection can race with socket release and access a freed socket. KASAN reported:   BUG: KASAN: slab-use-after-free in iso_sock_hold+0xf7/0x1b0   Call Trace:    iso_sock_hold+0xf7/0x1b0    iso_conn_del+0x7b/0x1d0    iso_connect_cfm+0x186/0x16a0    hci_conn_failed+0x154/0x280    hci_abort_conn_sync+0x3dc/0x7d0    hci_cmd_sync_work+0x173/0x300   Allocated by task 121:    sk_alloc+0x2b/0x6d0    bt_sock_alloc+0x29/0x370    iso_sock_alloc.constprop.0+0x19/0x300    iso_sock_create+0x94/0x100   Freed by task 121:    kfree+0x121/0x3c0    __sk_destruct+0x42b/0x540    iso_sock_releas…&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 164 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: Bluetooth: ISO: Serialize concurrent connect calls iso_sock_connect() checks the socket state before taking the socket lock and drops the lock again before setting up a connection. Two callers can both pass the admission check while the socket is open or bound. Caller A can copy its destination for route selection, then caller B can replace the socket destination before A binds or connects the CIS. A then uses B&amp;#39;s destination with the route selected for its own request. B can also proceed after A attaches a connection and sets BT_CONNECT. For deferred BIS setup, B can bind a second BIS and overwrite iso_pi(sk)-&amp;gt;conn, leaving the first connection&amp;#39;s reference and conn-&amp;gt;sk back-pointer stranded. Concurrent CIS connects can likewise replace the socket&amp;#39;s connection. Later teardown only detaches the current connection, so a callback on the old connection can race with socket release and access a freed socket. KASAN reported:   BUG: KASAN: slab-use-after-free in iso_sock_hold+0xf7/0x1b0   Call Trace:    iso_sock_hold+0xf7/0x1b0    iso_conn_del+0x7b/0x1d0    iso_connect_cfm+0x186/0x16a0    hci_conn_failed+0x154/0x280    hci_abort_conn_sync+0x3dc/0x7d0    hci_cmd_sync_work+0x173/0x300   Allocated by task 121:    sk_alloc+0x2b/0x6d0    bt_sock_alloc+0x29/0x370    iso_sock_alloc.constprop.0+0x19/0x300    iso_sock_create+0x94/0x100   Freed by task 121:    kfree+0x121/0x3c0    __sk_destruct+0x42b/0x540    iso_sock_releas…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2026-99012</guid>
    </item>
  </channel>
</rss>
