<?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 16:40:07 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-89711 — NFSD: remove flawed WARN_ON_ONCE from nfsd_mode_check</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-89711</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: remove flawed WARN_ON_ONCE from nfsd_mode_check&lt;/p&gt;
&lt;p&gt;The header for commit e75b23f9e323 (&amp;#34;nfsd: check d_can_lookup in
fh_verify of directories&amp;#34;) details the assumption that justified
adding the WARN_ON_ONCE to nfsd_mode_check(), that assumption is
invalid (in the case of NFS reexport).&lt;/p&gt;
&lt;p&gt;When NFSD exports an NFS filesystem it is very possible for
nfsd_mode_check() to encounter a @dentry that doesn&amp;#39;t have
i_op-&amp;gt;lookup (see nfs_fhget()&amp;#39;s NFS_ATTR_FATTR_MOUNTPOINT and
NFS_ATTR_FATTR_V4_REFERRAL handling, and d_flags_for_inode()).&lt;/p&gt;
&lt;p&gt;So remove nfsd_mode_check()&amp;#39;s WARN_ON_ONCE(). The nfserr_notdir
return on that branch must stay. It guards the subsequent
lookup_one_unlocked() -&amp;gt; __lookup_slow() path, which calls
inode-&amp;gt;i_op-&amp;gt;lookup() with no NULL check, so returning nfserr_notdir
is what keeps a client LOOKUP into such a @dentry from dereferencing
a NULL method pointer.&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: remove flawed WARN_ON_ONCE from nfsd_mode_check&lt;/p&gt;
&lt;p&gt;The header for commit e75b23f9e323 (&amp;#34;nfsd: check d_can_lookup in
fh_verify of directories&amp;#34;) details the assumption that justified
adding the WARN_ON_ONCE to nfsd_mode_check(), that assumption is
invalid (in the case of NFS reexport).&lt;/p&gt;
&lt;p&gt;When NFSD exports an NFS filesystem it is very possible for
nfsd_mode_check() to encounter a @dentry that doesn&amp;#39;t have
i_op-&amp;gt;lookup (see nfs_fhget()&amp;#39;s NFS_ATTR_FATTR_MOUNTPOINT and
NFS_ATTR_FATTR_V4_REFERRAL handling, and d_flags_for_inode()).&lt;/p&gt;
&lt;p&gt;So remove nfsd_mode_check()&amp;#39;s WARN_ON_ONCE(). The nfserr_notdir
return on that branch must stay. It guards the subsequent
lookup_one_unlocked() -&amp;gt; __lookup_slow() path, which calls
inode-&amp;gt;i_op-&amp;gt;lookup() with no NULL check, so returning nfserr_notdir
is what keeps a client LOOKUP into such a @dentry from dereferencing
a NULL method pointer.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-89711</guid>
    </item>
  </channel>
</rss>
