https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Tue, 06 Oct 2026 11:46:36 +0000 https://vulnerability.circl.lu/vuln/cve-2021-47416 <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>phy: mdio: fix memory leak</p> <p>Syzbot reported memory leak in MDIO bus interface, the problem was in wrong state logic.</p> <p>MDIOBUS_ALLOCATED indicates 2 states: 1. Bus is only allocated 2. Bus allocated and __mdiobus_register() fails, but device_register() was called</p> <p>In case of device_register() has been called we should call put_device() to correctly free the memory allocated for this device, but mdiobus_free() calls just kfree(dev) in case of MDIOBUS_ALLOCATED state</p> <p>To avoid this behaviour we need to set bus-&gt;state to MDIOBUS_UNREGISTERED _before_ calling device_register(), because put_device() should be called even in case of device_register() failure.</p> <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>phy: mdio: fix memory leak</p> <p>Syzbot reported memory leak in MDIO bus interface, the problem was in wrong state logic.</p> <p>MDIOBUS_ALLOCATED indicates 2 states: 1. Bus is only allocated 2. Bus allocated and __mdiobus_register() fails, but device_register() was called</p> <p>In case of device_register() has been called we should call put_device() to correctly free the memory allocated for this device, but mdiobus_free() calls just kfree(dev) in case of MDIOBUS_ALLOCATED state</p> <p>To avoid this behaviour we need to set bus-&gt;state to MDIOBUS_UNREGISTERED _before_ calling device_register(), because put_device() should be called even in case of device_register() failure.</p> https://vulnerability.circl.lu/vuln/cve-2021-47416