<?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://cve.radiocsirt.org</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, 03 Oct 2026 03:37:56 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-64141</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-64141</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://cve.radiocsirt.org/vuln/bell-cve-2026-64141</guid>
    </item>
    <item>
      <title>certfr-2026-avi-0926 — 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://cve.radiocsirt.org/vuln/certfr-2026-avi-0926</link>
      <description>certfr-2026-avi-0926</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-0926</guid>
    </item>
    <item>
      <title>EUVD-2026-348428</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-348428</link>
      <description>EUVD-2026-348428</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-348428</guid>
    </item>
    <item>
      <title>fkie_cve-2026-64141</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-64141</link>
      <description>&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;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://cve.radiocsirt.org/vuln/fkie_cve-2026-64141</guid>
    </item>
    <item>
      <title>GHSA-5c3g-3v2r-672g</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-5c3g-3v2r-672g</link>
      <description>&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;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://cve.radiocsirt.org/vuln/ghsa-5c3g-3v2r-672g</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-64141</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-64141</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 null pointer dereference in compare_guid_key() 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. 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. 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:   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/0xee…&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 null pointer dereference in compare_guid_key() 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. 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. 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:   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/0xee…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-64141</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-2403 — Linux Kernel: Mehrere Schwachstellen ermöglichen nicht spezifizierten Angriff</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2403</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, möglicherweise Sicherheitsmaßnahmen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen oder vertrauliche Informationen offenzulegen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, möglicherweise Sicherheitsmaßnahmen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen oder vertrauliche Informationen offenzulegen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2403</guid>
    </item>
  </channel>
</rss>
