https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Mon, 28 Sep 2026 23:51:58 +0000 https://vulnerability.circl.lu/vuln/cve-2023-52929 <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>nvmem: core: fix cleanup after dev_set_name()</p> <p>If dev_set_name() fails, we leak nvmem-&gt;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.</p> <p>This results in a slightly larger fix, but results in clear code.</p> <p>Note: this patch depends on &#34;nvmem: core: initialise nvmem-&gt;id early&#34; and &#34;nvmem: core: remove nvmem_config wp_gpio&#34;.</p> <p>[Srini: Fixed subject line and error code handing with wp_gpio while applying.]</p> <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>nvmem: core: fix cleanup after dev_set_name()</p> <p>If dev_set_name() fails, we leak nvmem-&gt;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.</p> <p>This results in a slightly larger fix, but results in clear code.</p> <p>Note: this patch depends on &#34;nvmem: core: initialise nvmem-&gt;id early&#34; and &#34;nvmem: core: remove nvmem_config wp_gpio&#34;.</p> <p>[Srini: Fixed subject line and error code handing with wp_gpio while applying.]</p> https://vulnerability.circl.lu/vuln/cve-2023-52929