<?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 23:04:53 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-99289 — ksmbd: fix app-instance non-durable supersede session UAF</title>
      <link>https://db.gcve.eu/vuln/cve-2026-99289</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ksmbd: fix app-instance non-durable supersede session UAF&lt;/p&gt;
&lt;p&gt;ksmbd_close_fd_app_instance_id() supersedes a prior open that has the
same AppInstanceId. It reaches that open&amp;#39;s session through opinfo-&amp;gt;sess.
This pointer is not refcounted.&lt;/p&gt;
&lt;p&gt;Session teardown detaches durable handles before it frees the session.
It does not detach a non-durable open. That open still points at the
session through opinfo-&amp;gt;sess after the session is freed. Another session
can supersede the open at the same time. The supersede then takes a
write lock through the stale pointer, in the freed session&amp;#39;s file table.&lt;/p&gt;
&lt;p&gt;BUG: KASAN: slab-use-after-free in _raw_write_lock+0x71/0xd0
  Call Trace:
   _raw_write_lock+0x71/0xd0
   ksmbd_close_fd_app_instance_id+0xd9/0x670 [ksmbd]
   smb2_open+0x3e10/0xd910 [ksmbd]
  Freed by task 212:
   ksmbd_session_destroy+0x38d/0x480 [ksmbd]&lt;/p&gt;
&lt;p&gt;Fix this by looking the session up by opinfo-&amp;gt;session_id. The lookup
returns a reference, as smb2_break_collect_channels() does. Recheck that
opinfo-&amp;gt;sess still points at it before using it.&lt;/p&gt;
&lt;p&gt;Do the lookup without m_lock held. destroy_previous_session() takes
m_lock under the session table lock, and taking them in the other order
here would deadlock.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ksmbd: fix app-instance non-durable supersede session UAF&lt;/p&gt;
&lt;p&gt;ksmbd_close_fd_app_instance_id() supersedes a prior open that has the
same AppInstanceId. It reaches that open&amp;#39;s session through opinfo-&amp;gt;sess.
This pointer is not refcounted.&lt;/p&gt;
&lt;p&gt;Session teardown detaches durable handles before it frees the session.
It does not detach a non-durable open. That open still points at the
session through opinfo-&amp;gt;sess after the session is freed. Another session
can supersede the open at the same time. The supersede then takes a
write lock through the stale pointer, in the freed session&amp;#39;s file table.&lt;/p&gt;
&lt;p&gt;BUG: KASAN: slab-use-after-free in _raw_write_lock+0x71/0xd0
  Call Trace:
   _raw_write_lock+0x71/0xd0
   ksmbd_close_fd_app_instance_id+0xd9/0x670 [ksmbd]
   smb2_open+0x3e10/0xd910 [ksmbd]
  Freed by task 212:
   ksmbd_session_destroy+0x38d/0x480 [ksmbd]&lt;/p&gt;
&lt;p&gt;Fix this by looking the session up by opinfo-&amp;gt;session_id. The lookup
returns a reference, as smb2_break_collect_channels() does. Recheck that
opinfo-&amp;gt;sess still points at it before using it.&lt;/p&gt;
&lt;p&gt;Do the lookup without m_lock held. destroy_previous_session() takes
m_lock under the session table lock, and taking them in the other order
here would deadlock.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-99289</guid>
    </item>
  </channel>
</rss>
