<?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>Wed, 30 Sep 2026 03:39:14 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-74522 — ksmbd: fix use-after-free in __close_file_table_ids()</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-74522</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 in __close_file_table_ids()&lt;/p&gt;
&lt;p&gt;A ksmbd_file can remain alive after logical close while another session
holds a temporary reference obtained through ksmbd_lookup_fd_inode().
ksmbd_close_fd() currently marks the file closed and drops the idr-owned
reference, but leaves the pointer published in the closing session&amp;#39;s idr
until the final reference is dropped.&lt;/p&gt;
&lt;p&gt;If the foreign holder performs the final ksmbd_fd_put(), __put_fd_final()
supplies the foreign session&amp;#39;s file table to __ksmbd_close_fd(). The object
is then freed without being removed from its owner&amp;#39;s idr, and the owner
session later dereferences the stale pointer during file-table teardown.&lt;/p&gt;
&lt;p&gt;Remove the volatile id from the owner&amp;#39;s idr while ksmbd_close_fd() still
holds that table&amp;#39;s lock, and clear volatile_id before dropping
the idr-owned reference. A later foreign final put then only performs
physical destruction and cannot remove the object from the wrong table.&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 in __close_file_table_ids()&lt;/p&gt;
&lt;p&gt;A ksmbd_file can remain alive after logical close while another session
holds a temporary reference obtained through ksmbd_lookup_fd_inode().
ksmbd_close_fd() currently marks the file closed and drops the idr-owned
reference, but leaves the pointer published in the closing session&amp;#39;s idr
until the final reference is dropped.&lt;/p&gt;
&lt;p&gt;If the foreign holder performs the final ksmbd_fd_put(), __put_fd_final()
supplies the foreign session&amp;#39;s file table to __ksmbd_close_fd(). The object
is then freed without being removed from its owner&amp;#39;s idr, and the owner
session later dereferences the stale pointer during file-table teardown.&lt;/p&gt;
&lt;p&gt;Remove the volatile id from the owner&amp;#39;s idr while ksmbd_close_fd() still
holds that table&amp;#39;s lock, and clear volatile_id before dropping
the idr-owned reference. A later foreign final put then only performs
physical destruction and cannot remove the object from the wrong table.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-74522</guid>
    </item>
  </channel>
</rss>
