CVE-2023-52929: nvmem: core: fix cleanup after dev_set_name()
Noroxi assessment
Priority: Monitor (action score 22/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.24% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 23676ecd2eb377f7c24a6ff578b0f4c7135658b6, 39708bc8da7858de0bed9b3a88b3beb1d1e0b443, 560181d3ace61825f4ca9dd3481d6c0ee6709fa8.
Low priority for now. Upgrade to Linux Linux 23676ecd2eb377f7c24a6ff578b0f4c7135658b6, 39708bc8da7858de0bed9b3a88b3beb1d1e0b443, 560181d3ace61825f4ca9dd3481d6c0ee6709fa8 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.]
- Published
- Mar 27, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 15th percentile
- CWE
- CWE-459
Report tools
Action score
22
Monitor
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel6.1 and later · before 6.1.11
- linux linux kernel6.2
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 6.1affected
- a19a0f67dbb89ad2bfc466f2003841acba645884 and later · before 23676ecd2eb377f7c24a6ff578b0f4c7135658b6affected · git
- 14eea6449473c1f55e196cc104ba16d144465869 and later · before 8f9c4b2a3b132bf6698e477aba6ee194b40c75f4affected · git
- 5544e90c81261e82e02bbf7c6015a4b9c8c825ef and later · before 39708bc8da7858de0bed9b3a88b3beb1d1e0b443affected · git
- 5544e90c81261e82e02bbf7c6015a4b9c8c825ef and later · before 560181d3ace61825f4ca9dd3481d6c0ee6709fa8affected · git
- before 6.1not affected · semver
- 6.1.11 and later · up to and including 6.1.*not affected · semver
- 6.2 and laternot affected · original_commit_for_fix
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.11-1 | 6.1.11-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2022-49759Mar 27, 2025 · VMCI: Use threaded irqs instead of tasklets22Monitor
- ← EarlierCVE-2022-49761Mar 27, 2025 · btrfs: always report error in run_one_delayed_ref()31Monitor
- Later →CVE-2023-52930Mar 27, 2025 · drm/i915: Fix potential bit_17 double-free31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 23676ecd2eb377f7c24a6ff578b0f4c7135658b6 | Vendor (CNA) |
| Linux Linux | 39708bc8da7858de0bed9b3a88b3beb1d1e0b443 | Vendor (CNA) |
| Linux Linux | 560181d3ace61825f4ca9dd3481d6c0ee6709fa8 | Vendor (CNA) |
| Linux Linux | 8f9c4b2a3b132bf6698e477aba6ee194b40c75f4 | Vendor (CNA) |
| debian:linux | 6.1.11-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-31668393 days apartseg6: separate dst_cache for input and output paths in seg6 lwtunnel39Monitor
- CVE-2025-3790854 days apartmm, slab: clean up slab->obj_exts always31Monitor
- CVE-2021-47110377 days apartx86/kvm: Disable kvmclock on all CPUs on shutdown28Monitor
- CVE-2024-47693157 days apartIB/core: Fix ib_cache_setup_one error flow cleanup26Monitor
- CVE-2025-219245 days apartnet: hns3: make sure ptp clock is unregister and freed if hclge_ptp_get_cycle returns an error22Monitor
- CVE-2024-5797528 days apartbtrfs: do proper folio cleanup when run_delalloc_nocow() failed22Monitor
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-459 · Incomplete CleanupCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.