linux-cve-announce - CVE-2023-52929: nvmem: core: fix cleanup after dev_set

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: <2025032719-CVE-2023-52929-7900@gregkh>
Date: Thu, 27 Mar 2025 17:37:19 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: CVE-2023-52929: nvmem: core: fix cleanup after dev_set_name()

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

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

nvmem: core: fix cleanup after dev_set_name()

If dev_set_name() fails, we leak nvmem->wp_gpio as the cleanup does not
put this. While a minimal fix for this would be to add the gpiod_put()
call, we can do better if we split device_register(), and use the
tested nvmem_release() cleanup code by initialising the device early,
and putting the device.

This results in a slightly larger fix, but results in clear code.

Note: this patch depends on "nvmem: core: initialise nvmem->id early"
and "nvmem: core: remove nvmem_config wp_gpio".

[Srini: Fixed subject line and error code handing with wp_gpio while applying.]

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


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

	Issue introduced in 6.1 with commit 5544e90c81261e82e02bbf7c6015a4b9c8c825ef and fixed in 6.1.11 with commit 39708bc8da7858de0bed9b3a88b3beb1d1e0b443
	Issue introduced in 6.1 with commit 5544e90c81261e82e02bbf7c6015a4b9c8c825ef and fixed in 6.2 with commit 560181d3ace61825f4ca9dd3481d6c0ee6709fa8

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-52929
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:
	drivers/nvmem/core.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/23676ecd2eb377f7c24a6ff578b0f4c7135658b6
	https://git.kernel.org/stable/c/8f9c4b2a3b132bf6698e477aba6ee194b40c75f4
	https://git.kernel.org/stable/c/39708bc8da7858de0bed9b3a88b3beb1d1e0b443
	https://git.kernel.org/stable/c/560181d3ace61825f4ca9dd3481d6c0ee6709fa8