<?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>Sun, 04 Oct 2026 06:55:08 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-53026 — NFSD: fix nfs4_file access extra count in nfsd4_add_rdaccess_to_wrdeleg</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-53026</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 nfs4_file access extra count in nfsd4_add_rdaccess_to_wrdeleg&lt;/p&gt;
&lt;p&gt;In nfsd4_add_rdaccess_to_wrdeleg, if fp-&amp;gt;fi_fds[O_RDONLY] is already
set by another thread, __nfs4_file_get_access should not be called
to increment the nfs4_file access count since that was already done
by the thread that added READ access to the file. The extra fi_access
count in nfs4_file can prevent the corresponding nfsd_file from being
freed.&lt;/p&gt;
&lt;p&gt;When stopping nfs-server service, these extra access counts trigger a
BUG in kmem_cache_destroy() that shows nfsd_file object remaining on
__kmem_cache_shutdown.&lt;/p&gt;
&lt;p&gt;This problem can be reproduced by running the Git project&amp;#39;s test
suite over NFS.&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 nfs4_file access extra count in nfsd4_add_rdaccess_to_wrdeleg&lt;/p&gt;
&lt;p&gt;In nfsd4_add_rdaccess_to_wrdeleg, if fp-&amp;gt;fi_fds[O_RDONLY] is already
set by another thread, __nfs4_file_get_access should not be called
to increment the nfs4_file access count since that was already done
by the thread that added READ access to the file. The extra fi_access
count in nfs4_file can prevent the corresponding nfsd_file from being
freed.&lt;/p&gt;
&lt;p&gt;When stopping nfs-server service, these extra access counts trigger a
BUG in kmem_cache_destroy() that shows nfsd_file object remaining on
__kmem_cache_shutdown.&lt;/p&gt;
&lt;p&gt;This problem can be reproduced by running the Git project&amp;#39;s test
suite over NFS.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-53026</guid>
    </item>
  </channel>
</rss>
