<?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://vulnerability.circl.lu</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>Sun, 04 Oct 2026 08:45:48 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-64141 — ksmbd: fix null pointer dereference in compare_guid_key()</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-64141</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 null pointer dereference in compare_guid_key()&lt;/p&gt;
&lt;p&gt;session_fd_check() walks the per-inode m_op_list during durable-handle
session teardown and sets op-&amp;gt;conn = NULL for every opinfo whose conn
matched the closing session&amp;#39;s connection. The matching opinfo, however,
stays linked in its per-ClientGuid lease_table_list entry&amp;#39;s lb-&amp;gt;lease_list
because destroy_lease_table() only runs on full TCP-connection teardown,
not on SESSION_LOGOFF.&lt;/p&gt;
&lt;p&gt;If the same TCP connection then negotiates a fresh session with the
same ClientGuid (ClientGuid is bound to NEGOTIATE, not the session, and
is unchanged across LOGOFF + SETUP) and issues a SMB2 CREATE with a
lease context on a different inode, find_same_lease_key() walks
lb-&amp;gt;lease_list, reaches the stale opinfo, and calls compare_guid_key(),
which unconditionally dereferences opinfo-&amp;gt;conn-&amp;gt;ClientGUID. The conn
pointer is NULL and the kernel panics.&lt;/p&gt;
&lt;p&gt;Reproducer requires only a successful SMB2 SESSION_SETUP and a share
configured with &amp;#39;durable handles = yes&amp;#39;. KASAN report on mainline
70390501d194:&lt;/p&gt;
&lt;p&gt;general protection fault, probably for non-canonical address
  0xdffffc0000000069: 0000 [#1] SMP KASAN PTI
  KASAN: null-ptr-deref in range [0x0000000000000348-0x000000000000034f]
  Workqueue: ksmbd-io handle_ksmbd_work
  RIP: 0010:bcmp+0x5b/0x230
  Call Trace:
   compare_guid_key+0x4b/0xd0
   find_same_lease_key+0x324/0x690
   smb2_open+0x6aea/0x8e60
   handle_ksmbd_work+0x796…&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 null pointer dereference in compare_guid_key()&lt;/p&gt;
&lt;p&gt;session_fd_check() walks the per-inode m_op_list during durable-handle
session teardown and sets op-&amp;gt;conn = NULL for every opinfo whose conn
matched the closing session&amp;#39;s connection. The matching opinfo, however,
stays linked in its per-ClientGuid lease_table_list entry&amp;#39;s lb-&amp;gt;lease_list
because destroy_lease_table() only runs on full TCP-connection teardown,
not on SESSION_LOGOFF.&lt;/p&gt;
&lt;p&gt;If the same TCP connection then negotiates a fresh session with the
same ClientGuid (ClientGuid is bound to NEGOTIATE, not the session, and
is unchanged across LOGOFF + SETUP) and issues a SMB2 CREATE with a
lease context on a different inode, find_same_lease_key() walks
lb-&amp;gt;lease_list, reaches the stale opinfo, and calls compare_guid_key(),
which unconditionally dereferences opinfo-&amp;gt;conn-&amp;gt;ClientGUID. The conn
pointer is NULL and the kernel panics.&lt;/p&gt;
&lt;p&gt;Reproducer requires only a successful SMB2 SESSION_SETUP and a share
configured with &amp;#39;durable handles = yes&amp;#39;. KASAN report on mainline
70390501d194:&lt;/p&gt;
&lt;p&gt;general protection fault, probably for non-canonical address
  0xdffffc0000000069: 0000 [#1] SMP KASAN PTI
  KASAN: null-ptr-deref in range [0x0000000000000348-0x000000000000034f]
  Workqueue: ksmbd-io handle_ksmbd_work
  RIP: 0010:bcmp+0x5b/0x230
  Call Trace:
   compare_guid_key+0x4b/0xd0
   find_same_lease_key+0x324/0x690
   smb2_open+0x6aea/0x8e60
   handle_ksmbd_work+0x796…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-64141</guid>
    </item>
  </channel>
</rss>
