CVE-2023-52929nvmem: core: fix cleanup after dev_set_name()
- 5.5MediumCVSS base score
- 0.25%Exploitation in 30 daysEPSS · top 84% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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.]
Timeline
ID reserved
By Linux
- 7 months later
· 7 months later
Published
- 14 months later
· 14 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| NVDNVD · Analyzed | 3.1 | Medium5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
- EPSS (exploitation in 30 days)
- 0.25% · top 84% of all CVEs (17 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.
Affected products
- affected a19a0f67dbb89ad2bfc466f2003841acba645884 – < 23676ecd2eb377f7c24a6ff578b0f4c7135658b6
- affected 14eea6449473c1f55e196cc104ba16d144465869 – < 8f9c4b2a3b132bf6698e477aba6ee194b40c75f4
- affected 5544e90c81261e82e02bbf7c6015a4b9c8c825ef – < 39708bc8da7858de0bed9b3a88b3beb1d1e0b443
- affected 5544e90c81261e82e02bbf7c6015a4b9c8c825ef – < 560181d3ace61825f4ca9dd3481d6c0ee6709fa8
- affected 6.1
- unaffected < 6.1
- unaffected 6.1.11 – ≤ 6.1.*
- unaffected 6.2 – ≤ *
References
References4
- https://git.kernel.org/stable/c/23676ecd2eb377f7c24a6ff578b0f4c7135658b6 (opens in a new tab)
- https://git.kernel.org/stable/c/8f9c4b2a3b132bf6698e477aba6ee194b40c75f4 (opens in a new tab)
- https://git.kernel.org/stable/c/39708bc8da7858de0bed9b3a88b3beb1d1e0b443 (opens in a new tab)
- https://git.kernel.org/stable/c/560181d3ace61825f4ca9dd3481d6c0ee6709fa8 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2023-59761 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2023-52929)Record last updated .