<?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://db.gcve.eu</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>Mon, 16 Nov 2026 22:53:19 +0000</lastBuildDate>
    <item>
      <title>GHSA-jj2j-7jrj-28q3</title>
      <link>https://db.gcve.eu/vuln/ghsa-jj2j-7jrj-28q3</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ksmbd: fix use-after-free after a failed durable reconnect&lt;/p&gt;
&lt;p&gt;ksmbd_reopen_durable_fd() republishes a detached durable handle in the
reconnecting session&amp;#39;s file table and takes no reference for that entry.
If smb2_open() then fails, cleanup relies on the final ksmbd_fd_put() to
remove the volatile id.&lt;/p&gt;
&lt;p&gt;Two reconnects of the same handle can both take a lookup reference before
either attaches it. If the one that reopens first then fails and drops
its references first, the other request makes the final put through
ksmbd_put_durable_fd(). That frees the handle without removing the first
session&amp;#39;s table entry, so tearing that session down writes to freed
memory.&lt;/p&gt;
&lt;p&gt;BUG: KASAN: slab-use-after-free in __close_file_table_ids+0x14d/0x740 [ksmbd]
  Call Trace:
   __close_file_table_ids+0x14d/0x740 [ksmbd]
   ksmbd_destroy_file_table+0x76/0x100 [ksmbd]
   ksmbd_session_destroy+0xf8/0x480 [ksmbd]
   ksmbd_dispose_sessions+0x13e/0x200 [ksmbd]
   ksmbd_conn_sessions_cleanup+0x4c3/0x6d0 [ksmbd]
  Freed by task 1030:
   __ksmbd_close_fd+0x97d/0x1000 [ksmbd]
   smb2_open+0x14eb/0xd9f0 [ksmbd]&lt;/p&gt;
&lt;p&gt;Commit 3515503322f4 (&amp;#34;ksmbd: fix durable reconnect error path file
lifetime&amp;#34;) handles a final put made by the reconnecting request, but not
one made by another holder.&lt;/p&gt;
&lt;p&gt;Remove the volatile id under the file-table lock on this error path,
before the references are dropped, as ksmbd_close_fd() does on the
request_open path just above. Rem…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ksmbd: fix use-after-free after a failed durable reconnect&lt;/p&gt;
&lt;p&gt;ksmbd_reopen_durable_fd() republishes a detached durable handle in the
reconnecting session&amp;#39;s file table and takes no reference for that entry.
If smb2_open() then fails, cleanup relies on the final ksmbd_fd_put() to
remove the volatile id.&lt;/p&gt;
&lt;p&gt;Two reconnects of the same handle can both take a lookup reference before
either attaches it. If the one that reopens first then fails and drops
its references first, the other request makes the final put through
ksmbd_put_durable_fd(). That frees the handle without removing the first
session&amp;#39;s table entry, so tearing that session down writes to freed
memory.&lt;/p&gt;
&lt;p&gt;BUG: KASAN: slab-use-after-free in __close_file_table_ids+0x14d/0x740 [ksmbd]
  Call Trace:
   __close_file_table_ids+0x14d/0x740 [ksmbd]
   ksmbd_destroy_file_table+0x76/0x100 [ksmbd]
   ksmbd_session_destroy+0xf8/0x480 [ksmbd]
   ksmbd_dispose_sessions+0x13e/0x200 [ksmbd]
   ksmbd_conn_sessions_cleanup+0x4c3/0x6d0 [ksmbd]
  Freed by task 1030:
   __ksmbd_close_fd+0x97d/0x1000 [ksmbd]
   smb2_open+0x14eb/0xd9f0 [ksmbd]&lt;/p&gt;
&lt;p&gt;Commit 3515503322f4 (&amp;#34;ksmbd: fix durable reconnect error path file
lifetime&amp;#34;) handles a final put made by the reconnecting request, but not
one made by another holder.&lt;/p&gt;
&lt;p&gt;Remove the volatile id under the file-table lock on this error path,
before the references are dropped, as ksmbd_close_fd() does on the
request_open path just above. Rem…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-jj2j-7jrj-28q3</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-99290</title>
      <link>https://db.gcve.eu/vuln/ubuntu-cve-2026-99290</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 258 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: ksmbd: fix use-after-free after a failed durable reconnect ksmbd_reopen_durable_fd() republishes a detached durable handle in the reconnecting session&amp;#39;s file table and takes no reference for that entry. If smb2_open() then fails, cleanup relies on the final ksmbd_fd_put() to remove the volatile id. Two reconnects of the same handle can both take a lookup reference before either attaches it. If the one that reopens first then fails and drops its references first, the other request makes the final put through ksmbd_put_durable_fd(). That frees the handle without removing the first session&amp;#39;s table entry, so tearing that session down writes to freed memory.   BUG: KASAN: slab-use-after-free in __close_file_table_ids+0x14d/0x740 [ksmbd]   Call Trace:    __close_file_table_ids+0x14d/0x740 [ksmbd]    ksmbd_destroy_file_table+0x76/0x100 [ksmbd]    ksmbd_session_destroy+0xf8/0x480 [ksmbd]    ksmbd_dispose_sessions+0x13e/0x200 [ksmbd]    ksmbd_conn_sessions_cleanup+0x4c3/0x6d0 [ksmbd]   Freed by task 1030:    __ksmbd_close_fd+0x97d/0x1000 [ksmbd]    smb2_open+0x14eb/0xd9f0 [ksmbd] Commit 3515503322f4 (&amp;#34;ksmbd: fix durable reconnect error path file lifetime&amp;#34;) handles a final put made by the reconnecting request, but not one made by another holder. Remove the volatile id under the file-table lock on this error path, before the references are dropped, as ksmbd_close_fd() does on the request_open path just above. Removal t…&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 258 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: ksmbd: fix use-after-free after a failed durable reconnect ksmbd_reopen_durable_fd() republishes a detached durable handle in the reconnecting session&amp;#39;s file table and takes no reference for that entry. If smb2_open() then fails, cleanup relies on the final ksmbd_fd_put() to remove the volatile id. Two reconnects of the same handle can both take a lookup reference before either attaches it. If the one that reopens first then fails and drops its references first, the other request makes the final put through ksmbd_put_durable_fd(). That frees the handle without removing the first session&amp;#39;s table entry, so tearing that session down writes to freed memory.   BUG: KASAN: slab-use-after-free in __close_file_table_ids+0x14d/0x740 [ksmbd]   Call Trace:    __close_file_table_ids+0x14d/0x740 [ksmbd]    ksmbd_destroy_file_table+0x76/0x100 [ksmbd]    ksmbd_session_destroy+0xf8/0x480 [ksmbd]    ksmbd_dispose_sessions+0x13e/0x200 [ksmbd]    ksmbd_conn_sessions_cleanup+0x4c3/0x6d0 [ksmbd]   Freed by task 1030:    __ksmbd_close_fd+0x97d/0x1000 [ksmbd]    smb2_open+0x14eb/0xd9f0 [ksmbd] Commit 3515503322f4 (&amp;#34;ksmbd: fix durable reconnect error path file lifetime&amp;#34;) handles a final put made by the reconnecting request, but not one made by another holder. Remove the volatile id under the file-table lock on this error path, before the references are dropped, as ksmbd_close_fd() does on the request_open path just above. Removal t…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ubuntu-cve-2026-99290</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-4573 — Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service</title>
      <link>https://db.gcve.eu/vuln/wid-sec-w-2026-4573</link>
      <description>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/wid-sec-w-2026-4573</guid>
    </item>
  </channel>
</rss>
