From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2022-50853: NFSv4: Fix a credential leak in _nfs4_discover_trunking()
Date: Tue, 30 Dec 2025 13:19:49 +0100 [thread overview]
Message-ID: <2025123045-CVE-2022-50853-ceca@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
NFSv4: Fix a credential leak in _nfs4_discover_trunking()
The Linux kernel CVE team has assigned CVE-2022-50853 to this issue.
Affected and fixed versions
===========================
Issue introduced in 5.15.77 with commit ead049562758cc415437c0e99b09ce5eb2ab3dc0 and fixed in 5.15.86 with commit c6aca4c7ba8f6d40a0cfeeb09160dd8efdf97c64
Issue introduced in 5.19 with commit 4f40a5b5544618b096d1611a18219dd91fd57f80 and fixed in 6.0.16 with commit dfad5d5e7511933c2ae3d12a8131840074c5a73d
Issue introduced in 5.19 with commit 4f40a5b5544618b096d1611a18219dd91fd57f80 and fixed in 6.1.2 with commit b247a9828f6607d41189fa6c2a3be754d33cae86
Issue introduced in 5.19 with commit 4f40a5b5544618b096d1611a18219dd91fd57f80 and fixed in 6.2 with commit e83458fce080dc23c25353a1af90bfecf79c7369
Issue introduced in 5.18.10 with commit 2f42531f545f2670192b894d14d50e0539e47e24
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-50853
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/c6aca4c7ba8f6d40a0cfeeb09160dd8efdf97c64
https://git.kernel.org/stable/c/dfad5d5e7511933c2ae3d12a8131840074c5a73d
https://git.kernel.org/stable/c/b247a9828f6607d41189fa6c2a3be754d33cae86
https://git.kernel.org/stable/c/e83458fce080dc23c25353a1af90bfecf79c7369
reply other threads:[~2025-12-30 12:20 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=2025123045-CVE-2022-50853-ceca@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.