net: phy: sfp: free mii_bus in sfp_i2c_mdiobus_destroy
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ e85b1347ace677c3822c12d9332dfaaffe594da6 · < 8f31efff9206f9f0adb853cad6916086aac4d5ef| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
net: phy: sfp: free mii_bus in sfp_i2c_mdiobus_destroy
sfp_i2c_mdiobus_create() allocates the I2C MDIO bus with mdio_i2c_alloc(), a plain (non-devm) allocation, and registers it. sfp_i2c_mdiobus_destroy() only unregisters the bus and clears sfp->i2c_mii without calling mdiobus_free(). As the only reference to the bus is then cleared, the struct mii_bus is leaked.
This is hit whenever a copper/RollBall SFP module that instantiated an MDIO bus is removed: sfp_sm_main() takes the global teardown path and calls sfp_i2c_mdiobus_destroy(). sfp_cleanup(), on driver unbind, frees sfp->i2c_mii directly, which is why the leak only triggered on module hot-removal and not on unbind.
Free the bus in sfp_i2c_mdiobus_destroy() to match the allocation done in sfp_i2c_mdiobus_create().
From the CVE record · Linux
The Linux kernel leaks an allocated MDIO bus when a copper or RollBall SFP module that instantiated the bus is hot-removed. The input does not describe an attacker-controlled path, authentication requirements, or user interaction.
Engineers running Linux kernels with copper or RollBall SFP modules that instantiate an MDIO bus should check their systems; affected versions are not specified.