CVE-2023-52929 [Medium] | Information Disclosure in Linux Kernel

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.]

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2026-05-07	0.07%	0.04%	-0.02%
2	2026-01-21	0.02%	0.07%	+0.05%
3	2025-03-28	—	0.02%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2026-05-07

0.07%

0.04%

-0.02%

2026-01-21

0.02%

0.07%

+0.05%

2025-03-28

—

0.02%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
5.5	3.1	MEDIUM	`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H` Click to expand Attack vector (AV:L) They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by. Attack complexity (AC:L) Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup. Privileges required (PR:L) A normal user session is enough; they don’t have to be admin. User interaction (UI:N) Nobody has to click “OK” or open a trap file; it can work without a victim helping. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:N) Doesn’t really leak secrets in a meaningful way. Integrity (I:N) Data isn’t meaningfully altered or forged. Availability (A:H) Could take the service down hard or make it unusable for people who depend on it.	1.8	3.6	[email protected]

Base score

Version

Severity

Vector

Exploitability

Impact

Score source

5.5

3.1

MEDIUM

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H Click to expand

Attack vector (AV:L): They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L): Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L): A normal user session is enough; they don’t have to be admin.
User interaction (UI:N): Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N): Doesn’t really leak secrets in a meaningful way.
Integrity (I:N): Data isn’t meaningfully altered or forged.
Availability (A:H): Could take the service down hard or make it unusable for people who depend on it.

1.8

3.6

[email protected]

OS Trackers for CVE-2023-52929

vendor	priority	summary	link
`debian`	not yet assigned	CVE-2023-52929 not yet assigned priority: Debian including 1 source packages (linux), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5.	https://security-tracker.debian.org/tracker/CVE-2023-52929
`redhat`	low	—	https://access.redhat.com/security/cve/CVE-2023-52929
`suse`	medium	CVE-2023-52929 severity moderate: SUSE including 26 source package names (cluster-md-kmp-default, dlm-kmp-default, …), 239 product×package rows across 44 product lines (SLES-LTSS-TERADATA 15 SP2, SUSE Linux Enterprise High Performance Computing 15 SP3-LTSS, … (44 product lines)): Known Not Affected 239.	https://www.suse.com/security/cve/CVE-2023-52929/
`ubuntu`	medium	CVE-2023-52929 medium priority: Ubuntu including 130 source packages (linux, linux-allwinner-5.19, …), 1040 status rows across 8 suites (bionic, focal, jammy, noble, oracular, trusty, upstream, xenial): DNE 713, ignored 146, not-affected 117, released 64.	https://ubuntu.com/security/CVE-2023-52929

Affected software / configurations for CVE-2023-52929

Vendor	Product	Version	Raw CPE
linux	linux_kernel	>= 6.1, < 6.1.11	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	6.2	cpe:2.3:o:linux:linux_kernel:6.2:rc1::::::
linux	linux_kernel	6.2	cpe:2.3:o:linux:linux_kernel:6.2:rc2::::::
linux	linux_kernel	6.2	cpe:2.3:o:linux:linux_kernel:6.2:rc3::::::
linux	linux_kernel	6.2	cpe:2.3:o:linux:linux_kernel:6.2:rc4::::::
linux	linux_kernel	6.2	cpe:2.3:o:linux:linux_kernel:6.2:rc5::::::
linux	linux_kernel	6.2	cpe:2.3:o:linux:linux_kernel:6.2:rc6::::::

References for CVE-2023-52929

URL	Tags
https://git.kernel.org/stable/c/23676ecd2eb377f7c24a6ff578b0f4c7135658b6	Patch
https://git.kernel.org/stable/c/39708bc8da7858de0bed9b3a88b3beb1d1e0b443	Patch
https://git.kernel.org/stable/c/560181d3ace61825f4ca9dd3481d6c0ee6709fa8	Patch
https://git.kernel.org/stable/c/8f9c4b2a3b132bf6698e477aba6ee194b40c75f4	Patch

URL

CVE-2023-52929 | nvmem: core: fix cleanup after dev_set_name()

Exploit prediction scoring system (EPSS) score for CVE-2023-52929

Common vulnerability scoring system (CVSS) metrics for CVE-2023-52929

Weakness enumeration for CVE-2023-52929

OS Trackers for CVE-2023-52929

Affected software / configurations for CVE-2023-52929

References for CVE-2023-52929