<?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://cve.radiocsirt.org</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>Mon, 05 Oct 2026 08:04:03 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-89677 — nfsd: fix possible fh_compose of wrong dentry in nfsd4_create_file()</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-89677</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 possible fh_compose of wrong dentry in nfsd4_create_file()&lt;/p&gt;
&lt;p&gt;dentry_create() can hypothetically provide a different dentry than the
one passed in.  This could happen, for example, if the exported
filesystem is NFS, and the server returned to OPEN a filehandle which
matched a directory that was already in the dcache.  Clearly this would
not be expected!&lt;/p&gt;
&lt;p&gt;If this were to happen the dentry (child) that was already stored in
resfhp could be freed and later dereferenced.&lt;/p&gt;
&lt;p&gt;We shouldn&amp;#39;t call fh_compose() until we are certain that we have the
final dentry, so this patch moved the fh_compose() call to two places:
one for the case where the target already exists, and one after
dentry_create() where it was created.&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 possible fh_compose of wrong dentry in nfsd4_create_file()&lt;/p&gt;
&lt;p&gt;dentry_create() can hypothetically provide a different dentry than the
one passed in.  This could happen, for example, if the exported
filesystem is NFS, and the server returned to OPEN a filehandle which
matched a directory that was already in the dcache.  Clearly this would
not be expected!&lt;/p&gt;
&lt;p&gt;If this were to happen the dentry (child) that was already stored in
resfhp could be freed and later dereferenced.&lt;/p&gt;
&lt;p&gt;We shouldn&amp;#39;t call fh_compose() until we are certain that we have the
final dentry, so this patch moved the fh_compose() call to two places:
one for the case where the target already exists, and one after
dentry_create() where it was created.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-89677</guid>
    </item>
  </channel>
</rss>
