From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-74730: NFS: Pin the 'struct nfs_server' during a FREE_STATEID call
Date: Sat, 22 Aug 2026 17:33:34 +0200 [thread overview]
Message-ID: <2026082242-CVE-2026-74730-e35d@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
NFS: Pin the 'struct nfs_server' during a FREE_STATEID call
Dan Aloni reports that he was able to hit a use-after-free bug if a
FREE_STATEID operation gets delayed for whatever reason. Fix this by
bumping the refcount of the 'struct nfs_server' object for the duration
of the FREE_STATEID so it doesn't get cleaned up from underneath us
while operations are still in flight.
The Linux kernel CVE team has assigned CVE-2026-74730 to this issue.
Affected and fixed versions
===========================
Issue introduced in 3.10 with commit 7c1d5fae4a87d3cf3e9ffd68bcdbaf6529013009 and fixed in 5.10.265 with commit ed2f92ce2fc48463c41e0e540b9a3454889e8af8
Issue introduced in 3.10 with commit 7c1d5fae4a87d3cf3e9ffd68bcdbaf6529013009 and fixed in 5.15.216 with commit d858ab09e787106432d4d9830bad9dfedf02f890
Issue introduced in 3.10 with commit 7c1d5fae4a87d3cf3e9ffd68bcdbaf6529013009 and fixed in 6.1.183 with commit af62f1af182d33a0de38308c012841885d8ab92e
Issue introduced in 3.10 with commit 7c1d5fae4a87d3cf3e9ffd68bcdbaf6529013009 and fixed in 6.6.152 with commit caee6a68ffaa5016dfc01cd0b3dc1896a32e3abd
Issue introduced in 3.10 with commit 7c1d5fae4a87d3cf3e9ffd68bcdbaf6529013009 and fixed in 6.12.104 with commit ed1161ab6239761958b38d5667225634fc2be894
Issue introduced in 3.10 with commit 7c1d5fae4a87d3cf3e9ffd68bcdbaf6529013009 and fixed in 6.18.45 with commit d71dfffa512e71b166a889484e4c3b148a9a3af2
Issue introduced in 3.10 with commit 7c1d5fae4a87d3cf3e9ffd68bcdbaf6529013009 and fixed in 7.1.9 with commit 80ed3d762628b36c9e4b22fac7c65b72ef3b13dd
Issue introduced in 3.10 with commit 7c1d5fae4a87d3cf3e9ffd68bcdbaf6529013009 and fixed in 7.2 with commit cf616096a0f3a2b60f7d68b6b39674a6867ded9c
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-74730
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/nfs4proc.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/ed2f92ce2fc48463c41e0e540b9a3454889e8af8
https://git.kernel.org/stable/c/d858ab09e787106432d4d9830bad9dfedf02f890
https://git.kernel.org/stable/c/af62f1af182d33a0de38308c012841885d8ab92e
https://git.kernel.org/stable/c/caee6a68ffaa5016dfc01cd0b3dc1896a32e3abd
https://git.kernel.org/stable/c/ed1161ab6239761958b38d5667225634fc2be894
https://git.kernel.org/stable/c/d71dfffa512e71b166a889484e4c3b148a9a3af2
https://git.kernel.org/stable/c/80ed3d762628b36c9e4b22fac7c65b72ef3b13dd
https://git.kernel.org/stable/c/cf616096a0f3a2b60f7d68b6b39674a6867ded9c
reply other threads:[~2026-08-22 15:40 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=2026082242-CVE-2026-74730-e35d@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.