linux-cve-announce - CVE-2022-49927: nfs4: Fix kmemleak when allocate slot failed

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: <2025050110-CVE-2022-49927-461e@gregkh>
Date: Thu,  1 May 2025 16:11:57 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2022-49927: nfs4: Fix kmemleak when allocate slot failed

From: Greg Kroah-Hartman <gregkh@...nel.org>

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

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

nfs4: Fix kmemleak when allocate slot failed

If one of the slot allocate failed, should cleanup all the other
allocated slots, otherwise, the allocated slots will leak:

  unreferenced object 0xffff8881115aa100 (size 64):
    comm ""mount.nfs"", pid 679, jiffies 4294744957 (age 115.037s)
    hex dump (first 32 bytes):
      00 cc 19 73 81 88 ff ff 00 a0 5a 11 81 88 ff ff  ...s......Z.....
      00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
    backtrace:
      [<000000007a4c434a>] nfs4_find_or_create_slot+0x8e/0x130
      [<000000005472a39c>] nfs4_realloc_slot_table+0x23f/0x270
      [<00000000cd8ca0eb>] nfs40_init_client+0x4a/0x90
      [<00000000128486db>] nfs4_init_client+0xce/0x270
      [<000000008d2cacad>] nfs4_set_client+0x1a2/0x2b0
      [<000000000e593b52>] nfs4_create_server+0x300/0x5f0
      [<00000000e4425dd2>] nfs4_try_get_tree+0x65/0x110
      [<00000000d3a6176f>] vfs_get_tree+0x41/0xf0
      [<0000000016b5ad4c>] path_mount+0x9b3/0xdd0
      [<00000000494cae71>] __x64_sys_mount+0x190/0x1d0
      [<000000005d56bdec>] do_syscall_64+0x35/0x80
      [<00000000687c9ae4>] entry_SYSCALL_64_after_hwframe+0x46/0xb0

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


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

	Issue introduced in 3.12 with commit abf79bb341bf52f75f295b850abdf5f78f584311 and fixed in 4.9.333 with commit 84b5cb476903003ae9ca88f32b57ff0eaefa6d4c
	Issue introduced in 3.12 with commit abf79bb341bf52f75f295b850abdf5f78f584311 and fixed in 4.14.299 with commit aae35a0c8a775fa4afa6a4e7dab3f936f1f89bbb
	Issue introduced in 3.12 with commit abf79bb341bf52f75f295b850abdf5f78f584311 and fixed in 4.19.265 with commit 86ce0e93cf6fb4d0c447323ac66577c642628b9d
	Issue introduced in 3.12 with commit abf79bb341bf52f75f295b850abdf5f78f584311 and fixed in 5.4.224 with commit 925cb538bd5851154602818dc80bf4b4d924c127
	Issue introduced in 3.12 with commit abf79bb341bf52f75f295b850abdf5f78f584311 and fixed in 5.10.154 with commit 45aea4fbf61e205649c29200726b9f45c1718a67
	Issue introduced in 3.12 with commit abf79bb341bf52f75f295b850abdf5f78f584311 and fixed in 5.15.78 with commit 24641993a7dce6b1628645f4e1d97ca06c9f765d
	Issue introduced in 3.12 with commit abf79bb341bf52f75f295b850abdf5f78f584311 and fixed in 6.0.8 with commit db333ae981fb8843c383aa7dbf62cc682597d401
	Issue introduced in 3.12 with commit abf79bb341bf52f75f295b850abdf5f78f584311 and fixed in 6.1 with commit 7e8436728e22181c3f12a5dbabd35ed3a8b8c593

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-49927
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/nfs4client.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/84b5cb476903003ae9ca88f32b57ff0eaefa6d4c
	https://git.kernel.org/stable/c/aae35a0c8a775fa4afa6a4e7dab3f936f1f89bbb
	https://git.kernel.org/stable/c/86ce0e93cf6fb4d0c447323ac66577c642628b9d
	https://git.kernel.org/stable/c/925cb538bd5851154602818dc80bf4b4d924c127
	https://git.kernel.org/stable/c/45aea4fbf61e205649c29200726b9f45c1718a67
	https://git.kernel.org/stable/c/24641993a7dce6b1628645f4e1d97ca06c9f765d
	https://git.kernel.org/stable/c/db333ae981fb8843c383aa7dbf62cc682597d401
	https://git.kernel.org/stable/c/7e8436728e22181c3f12a5dbabd35ed3a8b8c593