From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2022-50385: NFS: Fix an Oops in nfs_d_automount()
Date: Thu, 18 Sep 2025 15:33:59 +0200 [thread overview]
Message-ID: <2025091852-CVE-2022-50385-7787@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
NFS: Fix an Oops in nfs_d_automount()
When mounting from a NFSv4 referral, path->dentry can end up being a
negative dentry, so derive the struct nfs_server from the dentry
itself instead.
The Linux kernel CVE team has assigned CVE-2022-50385 to this issue.
Affected and fixed versions
===========================
Issue introduced in 4.1 with commit 2b0143b5c986be1ce8408b3aadc4709e0a94429d and fixed in 5.10.163 with commit 5458bc0f9df639d83471ca384152cc62dbee0aeb
Issue introduced in 4.1 with commit 2b0143b5c986be1ce8408b3aadc4709e0a94429d and fixed in 5.15.86 with commit f12377abac15fb4e8698225ac386894f8ae63598
Issue introduced in 4.1 with commit 2b0143b5c986be1ce8408b3aadc4709e0a94429d and fixed in 6.0.16 with commit b6fd25d64b0de27991d6bd677f0adf69ad6ff07a
Issue introduced in 4.1 with commit 2b0143b5c986be1ce8408b3aadc4709e0a94429d and fixed in 6.1.2 with commit 6f3d56783fbed861e483736a7001bdafd0dddd53
Issue introduced in 4.1 with commit 2b0143b5c986be1ce8408b3aadc4709e0a94429d and fixed in 6.2 with commit 35e3b6ae84935d0d7ff76cbdaa83411b0ad5e471
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-2022-50385
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/namespace.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/5458bc0f9df639d83471ca384152cc62dbee0aeb
https://git.kernel.org/stable/c/f12377abac15fb4e8698225ac386894f8ae63598
https://git.kernel.org/stable/c/b6fd25d64b0de27991d6bd677f0adf69ad6ff07a
https://git.kernel.org/stable/c/6f3d56783fbed861e483736a7001bdafd0dddd53
https://git.kernel.org/stable/c/35e3b6ae84935d0d7ff76cbdaa83411b0ad5e471
reply other threads:[~2025-09-18 13:34 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=2025091852-CVE-2022-50385-7787@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.