CVE-2023-52929
nvmem: core: fix cleanup after dev_set_name()
We use these services and cookies to improve your user experience. You may opt out if you wish, however, this may limit some features on this site.
Please see our statement on Data Privacy.
nvmem: core: fix cleanup after dev_set_name()
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.]
Reserved 2024-08-21 | Published 2025-03-27 | Updated 2025-05-04 | Assigner Linuxgit.kernel.org/...c/23676ecd2eb377f7c24a6ff578b0f4c7135658b6
git.kernel.org/...c/8f9c4b2a3b132bf6698e477aba6ee194b40c75f4
git.kernel.org/...c/39708bc8da7858de0bed9b3a88b3beb1d1e0b443
git.kernel.org/...c/560181d3ace61825f4ca9dd3481d6c0ee6709fa8
Support options
