linux-cve-announce - CVE-2023-53241: nfsd: call op_release, even when op

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: <2025091516-CVE-2023-53241-c75a@gregkh>
Date: Mon, 15 Sep 2025 16:22:15 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2023-53241: nfsd: call op_release, even when op_func returns an error

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

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

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

nfsd: call op_release, even when op_func returns an error

For ops with "trivial" replies, nfsd4_encode_operation will shortcut
most of the encoding work and skip to just marshalling up the status.
One of the things it skips is calling op_release. This could cause a
memory leak in the layoutget codepath if there is an error at an
inopportune time.

Have the compound processing engine always call op_release, even when
op_func sets an error in op->status. With this change, we also need
nfsd4_block_get_device_info_scsi to set the gd_device pointer to NULL
on error to avoid a double free.

The Linux kernel CVE team has assigned CVE-2023-53241 to this issue.


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

	Issue introduced in 4.14 with commit 34b1744c91ccd44811005822106945fa80ecbff2 and fixed in 5.10.220 with commit 65a33135e91e6dd661ecdf1194b9d90c49ae3570
	Issue introduced in 4.14 with commit 34b1744c91ccd44811005822106945fa80ecbff2 and fixed in 5.15.154 with commit b11d8162c24af4a351d21e2c804d25ca493305e3
	Issue introduced in 4.14 with commit 34b1744c91ccd44811005822106945fa80ecbff2 and fixed in 6.1.24 with commit b623a8e5d38a69a3ef8644acb1030dd7c7bc28b3
	Issue introduced in 4.14 with commit 34b1744c91ccd44811005822106945fa80ecbff2 and fixed in 6.2.11 with commit 3d0dcada384af22dec764c8374a2997870ec86ae
	Issue introduced in 4.14 with commit 34b1744c91ccd44811005822106945fa80ecbff2 and fixed in 6.3 with commit 15a8b55dbb1ba154d82627547c5761cac884d810

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-2023-53241
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/blocklayout.c
	fs/nfsd/nfs4xdr.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/65a33135e91e6dd661ecdf1194b9d90c49ae3570
	https://git.kernel.org/stable/c/b11d8162c24af4a351d21e2c804d25ca493305e3
	https://git.kernel.org/stable/c/b623a8e5d38a69a3ef8644acb1030dd7c7bc28b3
	https://git.kernel.org/stable/c/3d0dcada384af22dec764c8374a2997870ec86ae
	https://git.kernel.org/stable/c/15a8b55dbb1ba154d82627547c5761cac884d810