<?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>Tue, 29 Sep 2026 03:31:03 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-97556 — smb: client: avoid leaking refcount when cifs_sb_tlink() fails</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-97556</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;smb: client: avoid leaking refcount when cifs_sb_tlink() fails&lt;/p&gt;
&lt;p&gt;cifs_oplock_break() takes over the reference that
cifs_queue_oplock_break() acquired when it queued the work, and drops it
with _cifsFileInfo_put() once the break has been processed.&lt;/p&gt;
&lt;p&gt;Only in setups with &amp;#34;-o multiuser&amp;#34;, cifs_sb_tlink() may fail, at which
point cifs_oplock_break() returns without putting the file reference,
mirroring the reference leak we already fixed in the companion patch to
cifs_queue_oplock_break().&lt;/p&gt;
&lt;p&gt;This would trigger a crash due to busy inodes on the next unmount:&lt;/p&gt;
&lt;p&gt;BUG: Dentry ... still in use (1) [unmount of cifs cifs]
  VFS: Busy inodes after unmount of cifs (cifs)&lt;/p&gt;
&lt;p&gt;Drop the reference on that path as well. Doing so before the out label
mirrors the normal path, which also puts the reference before
cifs_done_oplock_break().&lt;/p&gt;
&lt;p&gt;Found by Sashiko code review. The failure path was not exercised at
runtime.&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;smb: client: avoid leaking refcount when cifs_sb_tlink() fails&lt;/p&gt;
&lt;p&gt;cifs_oplock_break() takes over the reference that
cifs_queue_oplock_break() acquired when it queued the work, and drops it
with _cifsFileInfo_put() once the break has been processed.&lt;/p&gt;
&lt;p&gt;Only in setups with &amp;#34;-o multiuser&amp;#34;, cifs_sb_tlink() may fail, at which
point cifs_oplock_break() returns without putting the file reference,
mirroring the reference leak we already fixed in the companion patch to
cifs_queue_oplock_break().&lt;/p&gt;
&lt;p&gt;This would trigger a crash due to busy inodes on the next unmount:&lt;/p&gt;
&lt;p&gt;BUG: Dentry ... still in use (1) [unmount of cifs cifs]
  VFS: Busy inodes after unmount of cifs (cifs)&lt;/p&gt;
&lt;p&gt;Drop the reference on that path as well. Doing so before the out label
mirrors the normal path, which also puts the reference before
cifs_done_oplock_break().&lt;/p&gt;
&lt;p&gt;Found by Sashiko code review. The failure path was not exercised at
runtime.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-97556</guid>
    </item>
  </channel>
</rss>
