<?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>Sat, 03 Oct 2026 02:58:05 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-71090 — nfsd: fix nfsd_file reference leak in nfsd4_add_rdaccess_to_wrdeleg()</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2025-71090</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;nfsd: fix nfsd_file reference leak in nfsd4_add_rdaccess_to_wrdeleg()&lt;/p&gt;
&lt;p&gt;nfsd4_add_rdaccess_to_wrdeleg() unconditionally overwrites
fp-&amp;gt;fi_fds[O_RDONLY] with a newly acquired nfsd_file. However, if
the client already has a SHARE_ACCESS_READ open from a previous OPEN
operation, this action overwrites the existing pointer without
releasing its reference, orphaning the previous reference.&lt;/p&gt;
&lt;p&gt;Additionally, the function originally stored the same nfsd_file
pointer in both fp-&amp;gt;fi_fds[O_RDONLY] and fp-&amp;gt;fi_rdeleg_file with
only a single reference. When put_deleg_file() runs, it clears
fi_rdeleg_file and calls nfs4_file_put_access() to release the file.&lt;/p&gt;
&lt;p&gt;However, nfs4_file_put_access() only releases fi_fds[O_RDONLY] when
the fi_access[O_RDONLY] counter drops to zero. If another READ open
exists on the file, the counter remains elevated and the nfsd_file
reference from the delegation is never released. This potentially
causes open conflicts on that file.&lt;/p&gt;
&lt;p&gt;Then, on server shutdown, these leaks cause __nfsd_file_cache_purge()
to encounter files with an elevated reference count that cannot be
cleaned up, ultimately triggering a BUG() in kmem_cache_destroy()
because there are still nfsd_file objects allocated in that cache.&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;nfsd: fix nfsd_file reference leak in nfsd4_add_rdaccess_to_wrdeleg()&lt;/p&gt;
&lt;p&gt;nfsd4_add_rdaccess_to_wrdeleg() unconditionally overwrites
fp-&amp;gt;fi_fds[O_RDONLY] with a newly acquired nfsd_file. However, if
the client already has a SHARE_ACCESS_READ open from a previous OPEN
operation, this action overwrites the existing pointer without
releasing its reference, orphaning the previous reference.&lt;/p&gt;
&lt;p&gt;Additionally, the function originally stored the same nfsd_file
pointer in both fp-&amp;gt;fi_fds[O_RDONLY] and fp-&amp;gt;fi_rdeleg_file with
only a single reference. When put_deleg_file() runs, it clears
fi_rdeleg_file and calls nfs4_file_put_access() to release the file.&lt;/p&gt;
&lt;p&gt;However, nfs4_file_put_access() only releases fi_fds[O_RDONLY] when
the fi_access[O_RDONLY] counter drops to zero. If another READ open
exists on the file, the counter remains elevated and the nfsd_file
reference from the delegation is never released. This potentially
causes open conflicts on that file.&lt;/p&gt;
&lt;p&gt;Then, on server shutdown, these leaks cause __nfsd_file_cache_purge()
to encounter files with an elevated reference count that cannot be
cleaned up, ultimately triggering a BUG() in kmem_cache_destroy()
because there are still nfsd_file objects allocated in that cache.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2025-71090</guid>
    </item>
  </channel>
</rss>
