Linux Kernel up to 6.1.10 nvmem dev_set_name cleanup

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
5.4$0-$5k0.00

Summaryinfo

A vulnerability classified as problematic has been found in Linux Kernel up to 6.1.10. This vulnerability affects the function dev_set_name of the component nvmem. Performing a manipulation results in an unknown weakness. This vulnerability is known as CVE-2023-52929. No exploit is available. It is recommended to upgrade the affected component.

Detailsinfo

A vulnerability, which was classified as problematic, was found in Linux Kernel up to 6.1.10. This affects the function dev_set_name of the component nvmem. CWE is classifying the issue as CWE-459. The product does not properly "clean up" and remove temporary or supporting resources after they have been used. The impact remains unknown. The summary by CVE is:

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

It is possible to read the advisory at git.kernel.org. This vulnerability is uniquely identified as CVE-2023-52929 since 08/21/2024. Technical details of the vulnerability are known, but there is no available exploit.

Upgrading to version 6.1.11 eliminates this vulnerability. Applying the patch 23676ecd2eb377f7c24a6ff578b0f4c7135658b6/8f9c4b2a3b132bf6698e477aba6ee194b40c75f4/39708bc8da7858de0bed9b3a88b3beb1d1e0b443/560181d3ace61825f4ca9dd3481d6c0ee6709fa8 is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.

The vulnerability is also documented in the vulnerability database at CERT Bund (WID-SEC-2025-0649). Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Affected

  • Google Container-Optimized OS
  • Debian Linux
  • Amazon Linux 2
  • Red Hat Enterprise Linux
  • Ubuntu Linux
  • SUSE Linux
  • Oracle Linux
  • SUSE openSUSE
  • Dell Avamar
  • Open Source Linux Kernel
  • SolarWinds Security Event Manager
  • Dell NetWorker
  • Dell Secure Connect Gateway

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.5
VulDB Meta Temp Score: 5.4

VulDB Base Score: 5.5
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 5.5
NVD Vector: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

Exploitinginfo

Class: Cleanup
CWE: CWE-459
CAPEC: 🔍
ATT&CK: 🔍

Physical: Partially
Local: Yes
Remote: Partially

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔍

Upgrade: Kernel 6.1.11
Patch: 23676ecd2eb377f7c24a6ff578b0f4c7135658b6/8f9c4b2a3b132bf6698e477aba6ee194b40c75f4/39708bc8da7858de0bed9b3a88b3beb1d1e0b443/560181d3ace61825f4ca9dd3481d6c0ee6709fa8

Timelineinfo

08/21/2024 🔍
03/27/2025 +218 days 🔍
03/27/2025 +0 days 🔍
12/07/2025 +255 days 🔍

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2023-52929 (🔍)
GCVE (CVE): GCVE-0-2023-52929
GCVE (VulDB): GCVE-100-301755
CERT Bund: WID-SEC-2025-0649 - Linux Kernel: Mehrere Schwachstellen

Entryinfo

Created: 03/27/2025 18:50
Updated: 12/07/2025 01:44
Changes: 03/27/2025 18:50 (57), 08/24/2025 07:49 (7), 10/28/2025 21:06 (12), 11/06/2025 08:40 (1), 12/07/2025 01:44 (1)
Complete: 🔍
Cache ID: 216::103

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

Do you need the next level of professionalism?

Upgrade your account now!