linux-cve-announce - CVE-2022-49418: NFSv4: Fix free of uninitialized nfs4

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <2025022653-CVE-2022-49418-ff01@gregkh>
Date: Wed, 26 Feb 2025 03:11:32 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: CVE-2022-49418: NFSv4: Fix free of uninitialized nfs4_label on referral lookup.

Description
===========

In the Linux kernel, the following vulnerability has been resolved:

NFSv4: Fix free of uninitialized nfs4_label on referral lookup.

Send along the already-allocated fattr along with nfs4_fs_locations, and
drop the memcpy of fattr.  We end up growing two more allocations, but this
fixes up a crash as:

PID: 790    TASK: ffff88811b43c000  CPU: 0   COMMAND: "ls"
 #0 [ffffc90000857920] panic at ffffffff81b9bfde
 #1 [ffffc900008579c0] do_trap at ffffffff81023a9b
 #2 [ffffc90000857a10] do_error_trap at ffffffff81023b78
 #3 [ffffc90000857a58] exc_stack_segment at ffffffff81be1f45
 #4 [ffffc90000857a80] asm_exc_stack_segment at ffffffff81c009de
 #5 [ffffc90000857b08] nfs_lookup at ffffffffa0302322 [nfs]
 #6 [ffffc90000857b70] __lookup_slow at ffffffff813a4a5f
 #7 [ffffc90000857c60] walk_component at ffffffff813a86c4
 #8 [ffffc90000857cb8] path_lookupat at ffffffff813a9553
 #9 [ffffc90000857cf0] filename_lookup at ffffffff813ab86b

The Linux kernel CVE team has assigned CVE-2022-49418 to this issue.


Affected and fixed versions
===========================

	Issue introduced in 5.16 with commit 9558a007dbc383d48e7f5a123d0b5ff656c71068 and fixed in 5.15.77 with commit eb1fe9600b86c24a789046bfc5c6851dda119280
	Issue introduced in 5.16 with commit 9558a007dbc383d48e7f5a123d0b5ff656c71068 and fixed in 5.18.3 with commit 6015292653d95ba9f72906e2b65e536aa5807d64
	Issue introduced in 5.16 with commit 9558a007dbc383d48e7f5a123d0b5ff656c71068 and fixed in 5.19 with commit c3ed222745d9ad7b69299b349a64ba533c64a34f

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-49418
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/nfs4namespace.c
	fs/nfs/nfs4proc.c
	fs/nfs/nfs4state.c
	fs/nfs/nfs4xdr.c
	include/linux/nfs_xdr.h


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/eb1fe9600b86c24a789046bfc5c6851dda119280
	https://git.kernel.org/stable/c/6015292653d95ba9f72906e2b65e536aa5807d64
	https://git.kernel.org/stable/c/c3ed222745d9ad7b69299b349a64ba533c64a34f