CyberRota Analysis
AI-GeneratedThe vulnerability affects the Linux kernel's handling of PHY devices, specifically when a PHY driver is unbound, leading to a potential NULL dereference. This can result in a system crash when attempting to access driver information for a detached PHY device. System administrators and developers managing Linux-based systems should prioritize addressing this issue to prevent potential service disruptions.
Original NVD Description
In the Linux kernel, the following vulnerability has been resolved: net: ethtool: phy: avoid NULL deref when PHY driver is unbound phydev->drv can become NULL while the phy_device is still attached to its net_device, namely after the PHY driver is unbound via sysfs: echo <mdio_id> > /sys/bus/mdio_bus/drivers/<phy_drv>/unbind phy_remove() clears phydev->drv but doesn't call phy_detach(), so the phy_device stays in the link topology xarray and ethnl_req_get_phydev() still hands it back. ETHTOOL_MSG_PHY_GET then oopses on: rep_data->drvname = kstrdup(phydev->drv->name, GFP_KERNEL); drvname is already treated as optional by phy_reply_size(), phy_fill_reply() and phy_cleanup_data(), so just skip the allocation when there is no driver bound.
Related CVEs
Other vulnerabilities affecting the same vendor(s)