Vulnerability 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.]
CVSS Score
MEDIUM
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux Kernel | >= 6.1, < 6.1.11 |
Related Weaknesses (CWE)
References
- https://git.kernel.org/stable/c/23676ecd2eb377f7c24a6ff578b0f4c7135658b6Patch
- https://git.kernel.org/stable/c/39708bc8da7858de0bed9b3a88b3beb1d1e0b443Patch
- https://git.kernel.org/stable/c/560181d3ace61825f4ca9dd3481d6c0ee6709fa8Patch
- https://git.kernel.org/stable/c/8f9c4b2a3b132bf6698e477aba6ee194b40c75f4Patch
FAQ
What is CVE-2023-52929?
CVE-2023-52929 is a vulnerability with a CVSS score of 5.5 (MEDIUM). 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. Wh...
How severe is CVE-2023-52929?
CVE-2023-52929 has been rated MEDIUM with a CVSS base score of 5.5/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2023-52929?
Check the references section above for vendor advisories and patch information. Affected products include: Linux Linux Kernel.