[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025041656-CVE-2024-58092-0938@gregkh>
Date: Wed, 16 Apr 2025 12:24:56 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: CVE-2024-58092: nfsd: fix legacy client tracking initialization
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
nfsd: fix legacy client tracking initialization
Get rid of the nfsd4_legacy_tracking_ops->init() call in
check_for_legacy_methods(). That will be handled in the caller
(nfsd4_client_tracking_init()). Otherwise, we'll wind up calling
nfsd4_legacy_tracking_ops->init() twice, and the second time we'll
trigger the BUG_ON() in nfsd4_init_recdir().
The Linux kernel CVE team has assigned CVE-2024-58092 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.8 with commit 74fd48739d0488e39ae18b0168720f449a06690c and fixed in 6.12.22 with commit 95407304253a4bf03494d921c6913e220c26cc63
Issue introduced in 6.8 with commit 74fd48739d0488e39ae18b0168720f449a06690c and fixed in 6.13.10 with commit cdd66082b227eb695cbf54b7c121ea032e869981
Issue introduced in 6.8 with commit 74fd48739d0488e39ae18b0168720f449a06690c and fixed in 6.14 with commit de71d4e211eddb670b285a0ea477a299601ce1ca
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-2024-58092
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/nfsd/nfs4recover.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/95407304253a4bf03494d921c6913e220c26cc63
https://git.kernel.org/stable/c/cdd66082b227eb695cbf54b7c121ea032e869981
https://git.kernel.org/stable/c/de71d4e211eddb670b285a0ea477a299601ce1ca
Powered by blists - more mailing lists