<?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>Fri, 02 Oct 2026 13:48:13 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-72381 — ksmbd: fix use-after-free of fp-&gt;owner.name in durable handle owner check</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-72381</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 use-after-free of fp-&amp;gt;owner.name in durable handle owner check&lt;/p&gt;
&lt;p&gt;Two concurrent SMB2 durable reconnects (DH2C/DHnC) on the same
persistent_id race the fp-&amp;gt;owner.name compare-read in
ksmbd_vfs_compare_durable_owner() against the kfree() in
ksmbd_reopen_durable_fd()&amp;#39;s reopen-success path. fp-&amp;gt;owner.name is a
standalone kstrdup() buffer whose lifetime is independent of the fp
refcount, and the two sites share no lock: the compare reads the buffer
while the reopen frees it, so the strcmp() can dereference freed memory.&lt;/p&gt;
&lt;p&gt;Commit 7ce4fc40018d (&amp;#34;ksmbd: fix durable reconnect double-bind race in
ksmbd_reopen_durable_fd&amp;#34;) made the fp-&amp;gt;conn claim atomic under
global_ft.lock (closing the owner.name double-free and the ksmbd_file
write-UAF), but the compare-read versus reopen-free pair was left
unserialized.&lt;/p&gt;
&lt;p&gt;BUG: KASAN: slab-use-after-free in strcmp+0x2c/0x80
  Read of size 1 by task kworker
    strcmp
    ksmbd_vfs_compare_durable_owner
    smb2_check_durable_oplock
    smb2_open
  Freed by task kworker:
    kfree
    ksmbd_reopen_durable_fd
    smb2_open
  Allocated by task kworker:
    kstrdup
    session_fd_check
    smb2_session_logoff
  The buggy address belongs to the cache kmalloc-8&lt;/p&gt;
&lt;p&gt;Serialize both sides of the race with fp-&amp;gt;f_lock.  The global durable
file-table lock still protects the durable reconnect claim, but
fp-&amp;gt;owner.name is per-open state and does not need to block unrelated
durable table lo…&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 use-after-free of fp-&amp;gt;owner.name in durable handle owner check&lt;/p&gt;
&lt;p&gt;Two concurrent SMB2 durable reconnects (DH2C/DHnC) on the same
persistent_id race the fp-&amp;gt;owner.name compare-read in
ksmbd_vfs_compare_durable_owner() against the kfree() in
ksmbd_reopen_durable_fd()&amp;#39;s reopen-success path. fp-&amp;gt;owner.name is a
standalone kstrdup() buffer whose lifetime is independent of the fp
refcount, and the two sites share no lock: the compare reads the buffer
while the reopen frees it, so the strcmp() can dereference freed memory.&lt;/p&gt;
&lt;p&gt;Commit 7ce4fc40018d (&amp;#34;ksmbd: fix durable reconnect double-bind race in
ksmbd_reopen_durable_fd&amp;#34;) made the fp-&amp;gt;conn claim atomic under
global_ft.lock (closing the owner.name double-free and the ksmbd_file
write-UAF), but the compare-read versus reopen-free pair was left
unserialized.&lt;/p&gt;
&lt;p&gt;BUG: KASAN: slab-use-after-free in strcmp+0x2c/0x80
  Read of size 1 by task kworker
    strcmp
    ksmbd_vfs_compare_durable_owner
    smb2_check_durable_oplock
    smb2_open
  Freed by task kworker:
    kfree
    ksmbd_reopen_durable_fd
    smb2_open
  Allocated by task kworker:
    kstrdup
    session_fd_check
    smb2_session_logoff
  The buggy address belongs to the cache kmalloc-8&lt;/p&gt;
&lt;p&gt;Serialize both sides of the race with fp-&amp;gt;f_lock.  The global durable
file-table lock still protects the durable reconnect claim, but
fp-&amp;gt;owner.name is per-open state and does not need to block unrelated
durable table lo…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-72381</guid>
    </item>
    <item>
      <title>USN-8816-1 — linux, linux-aws, linux-aws-7.0, linux-hwe-7.0, linux-ibm, linux-oracle, linux-raspi, linux-realtime vulnerabilities</title>
      <link>https://vulnerability.circl.lu/vuln/usn-8816-1</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:24.04:LTS: linux-aws-7.0, Ubuntu:24.04:LTS: linux-hwe-7.0, Ubuntu:26.04:LTS: linux, Ubuntu:26.04:LTS: linux-aws, Ubuntu:26.04:LTS: linux-ibm, Ubuntu:26.04:LTS: linux-oracle, Ubuntu:26.04:LTS: linux-raspi, Ubuntu:26.04:LTS: linux-realtime&lt;/p&gt;
&lt;p&gt;Several security issues were discovered in the Linux kernel.
An attacker could possibly use these to compromise the system.
This update corrects flaws in the following subsystems:
  - ARM64 architecture;
  - S390 architecture;
  - x86 architecture;
  - DRBD Distributed Replicated Block Device drivers;
  - InfiniBand drivers;
  - IOMMU subsystem;
  - Multiple devices driver;
  - Network drivers;
  - Microsoft Azure Network Adapter (MANA) driver;
  - NVME drivers;
  - TCM subsystem;
  - Virtio Host (VHOST) subsystem;
  - Xen hypervisor drivers;
  - AFS file system;
  - File systems infrastructure;
  - Network file systems library;
  - Network file system (NFS) client;
  - NTFS3 file system;
  - OCFS2 file system;
  - OrangeFS file system;
  - SMB network file system;
  - IPv4 networking;
  - Sun RPC protocol;
  - IPv6 networking;
  - IP tunnels definitions;
  - Netfilter;
  - TCP network protocol;
  - Locking primitives;
  - 9P file system network protocol;
  - B.A.T.M.A.N. meshing protocol;
  - Networking core;
  - IFE protocol;
  - RxRPC session sockets;
  - Network traffic control;
  - SCTP protocol;
  - SMC sockets;
  - TIPC protocol;
  - XFRM subsystem;
(CVE-2026-64530, CVE-2026-64534, CVE-2026-64535, CVE-2026-64541,
CVE-2026-64551, CVE-2026-68083, CVE-2026-68457, CVE-2026-68476,
CVE-2026-68477, CVE-2026-72014, CVE-2026-72020, CVE-2026-72033,
CVE-2026-72041, CVE-2026-72046, CVE-2026-72064, CVE-2026-72065,
CVE-2026-72069, CVE-2026-72083, CVE-2026-72084, CVE-2026-72085,
CVE…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:24.04:LTS: linux-aws-7.0, Ubuntu:24.04:LTS: linux-hwe-7.0, Ubuntu:26.04:LTS: linux, Ubuntu:26.04:LTS: linux-aws, Ubuntu:26.04:LTS: linux-ibm, Ubuntu:26.04:LTS: linux-oracle, Ubuntu:26.04:LTS: linux-raspi, Ubuntu:26.04:LTS: linux-realtime&lt;/p&gt;
&lt;p&gt;Several security issues were discovered in the Linux kernel.
An attacker could possibly use these to compromise the system.
This update corrects flaws in the following subsystems:
  - ARM64 architecture;
  - S390 architecture;
  - x86 architecture;
  - DRBD Distributed Replicated Block Device drivers;
  - InfiniBand drivers;
  - IOMMU subsystem;
  - Multiple devices driver;
  - Network drivers;
  - Microsoft Azure Network Adapter (MANA) driver;
  - NVME drivers;
  - TCM subsystem;
  - Virtio Host (VHOST) subsystem;
  - Xen hypervisor drivers;
  - AFS file system;
  - File systems infrastructure;
  - Network file systems library;
  - Network file system (NFS) client;
  - NTFS3 file system;
  - OCFS2 file system;
  - OrangeFS file system;
  - SMB network file system;
  - IPv4 networking;
  - Sun RPC protocol;
  - IPv6 networking;
  - IP tunnels definitions;
  - Netfilter;
  - TCP network protocol;
  - Locking primitives;
  - 9P file system network protocol;
  - B.A.T.M.A.N. meshing protocol;
  - Networking core;
  - IFE protocol;
  - RxRPC session sockets;
  - Network traffic control;
  - SCTP protocol;
  - SMC sockets;
  - TIPC protocol;
  - XFRM subsystem;
(CVE-2026-64530, CVE-2026-64534, CVE-2026-64535, CVE-2026-64541,
CVE-2026-64551, CVE-2026-68083, CVE-2026-68457, CVE-2026-68476,
CVE-2026-68477, CVE-2026-72014, CVE-2026-72020, CVE-2026-72033,
CVE-2026-72041, CVE-2026-72046, CVE-2026-72064, CVE-2026-72065,
CVE-2026-72069, CVE-2026-72083, CVE-2026-72084, CVE-2026-72085,
CVE…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/usn-8816-1</guid>
    </item>
  </channel>
</rss>
