From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-43470: nfs: return EISDIR on nfs3_proc_create if d_alias is a dir
Date: Fri, 8 May 2026 16:23:19 +0200 [thread overview]
Message-ID: <2026050804-CVE-2026-43470-27b3@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
nfs: return EISDIR on nfs3_proc_create if d_alias is a dir
If we found an alias through nfs3_do_create/nfs_add_or_obtain
/d_splice_alias which happens to be a dir dentry, we don't return
any error, and simply forget about this alias, but the original
dentry we were adding and passed as parameter remains negative.
This later causes an oops on nfs_atomic_open_v23/finish_open since we
supply a negative dentry to do_dentry_open.
This has been observed running lustre-racer, where dirs and files are
created/removed concurrently with the same name and O_EXCL is not
used to open files (frequent file redirection).
While d_splice_alias typically returns a directory alias or NULL, we
explicitly check d_is_dir() to ensure that we don't attempt to perform
file operations (like finish_open) on a directory inode, which triggers
the observed oops.
The Linux kernel CVE team has assigned CVE-2026-43470 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.10 with commit 7c6c5249f061b64fc6b5b90bc147169a048691bf and fixed in 6.12.78 with commit 7e2963773760a664684435201960dd2fb712f1b5
Issue introduced in 6.10 with commit 7c6c5249f061b64fc6b5b90bc147169a048691bf and fixed in 6.18.19 with commit 203c792cb4315360d49973ae2e57feeb6d3dcf7e
Issue introduced in 6.10 with commit 7c6c5249f061b64fc6b5b90bc147169a048691bf and fixed in 6.19.9 with commit 9ee1770fcb2f1b48354622b926e7dc10222805f5
Issue introduced in 6.10 with commit 7c6c5249f061b64fc6b5b90bc147169a048691bf and fixed in 7.0 with commit 410666a298c34ebd57256fde6b24c96bd23059a2
Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.
Unaffected versions might change over time as fixes are backported to
older supported kernel versions. The official CVE entry at
https://cve.org/CVERecord/?id=CVE-2026-43470
will be updated if fixes are backported, please check that for the most
up to date information about this issue.
Affected files
==============
The file(s) affected by this issue are:
fs/nfs/nfs3proc.c
Mitigation
==========
The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes. Individual
changes are never tested alone, but rather are part of a larger kernel
release. Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all. If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
https://git.kernel.org/stable/c/7e2963773760a664684435201960dd2fb712f1b5
https://git.kernel.org/stable/c/203c792cb4315360d49973ae2e57feeb6d3dcf7e
https://git.kernel.org/stable/c/9ee1770fcb2f1b48354622b926e7dc10222805f5
https://git.kernel.org/stable/c/410666a298c34ebd57256fde6b24c96bd23059a2
reply other threads:[~2026-05-08 14:27 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2026050804-CVE-2026-43470-27b3@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@kernel.org \
--cc=gregkh@kernel.org \
--cc=linux-cve-announce@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox