<?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 02:03:01 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-31718</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2026-31718</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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: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-31718</guid>
    </item>
    <item>
      <title>certfr-2026-avi-0831 — 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-2026-avi-0831</link>
      <description>certfr-2026-avi-0831</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2026-avi-0831</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-31718</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2026-31718</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 118 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: ksmbd: fix use-after-free in __ksmbd_close_fd() via durable scavenger When a durable file handle survives session disconnect (TCP close without SMB2_LOGOFF), session_fd_check() sets fp-&amp;gt;conn = NULL to preserve the handle for later reconnection. However, it did not clean up the byte-range locks on fp-&amp;gt;lock_list. Later, when the durable scavenger thread times out and calls __ksmbd_close_fd(NULL, fp), the lock cleanup loop did:     spin_lock(&amp;amp;fp-&amp;gt;conn-&amp;gt;llist_lock); This caused a slab use-after-free because fp-&amp;gt;conn was NULL and the original connection object had already been freed by ksmbd_tcp_disconnect(). The root cause is asymmetric cleanup: lock entries (smb_lock-&amp;gt;clist) were left dangling on the freed conn-&amp;gt;lock_list while fp-&amp;gt;conn was nulled out. To fix this issue properly, we need to handle the lifetime of smb_lock-&amp;gt;clist across three paths:  - Safely skip clist deletion when list is empty and fp-&amp;gt;conn is NULL.  - Remove the lock from the old connection&amp;#39;s lock_list in    session_fd_check()  - Re-add the lock to the new connection&amp;#39;s lock_list in    ksmbd_reopen_durable_fd().&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 118 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: ksmbd: fix use-after-free in __ksmbd_close_fd() via durable scavenger When a durable file handle survives session disconnect (TCP close without SMB2_LOGOFF), session_fd_check() sets fp-&amp;gt;conn = NULL to preserve the handle for later reconnection. However, it did not clean up the byte-range locks on fp-&amp;gt;lock_list. Later, when the durable scavenger thread times out and calls __ksmbd_close_fd(NULL, fp), the lock cleanup loop did:     spin_lock(&amp;amp;fp-&amp;gt;conn-&amp;gt;llist_lock); This caused a slab use-after-free because fp-&amp;gt;conn was NULL and the original connection object had already been freed by ksmbd_tcp_disconnect(). The root cause is asymmetric cleanup: lock entries (smb_lock-&amp;gt;clist) were left dangling on the freed conn-&amp;gt;lock_list while fp-&amp;gt;conn was nulled out. To fix this issue properly, we need to handle the lifetime of smb_lock-&amp;gt;clist across three paths:  - Safely skip clist deletion when list is empty and fp-&amp;gt;conn is NULL.  - Remove the lock from the old connection&amp;#39;s lock_list in    session_fd_check()  - Re-add the lock to the new connection&amp;#39;s lock_list in    ksmbd_reopen_durable_fd().&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2026-31718</guid>
    </item>
  </channel>
</rss>
