Impact
The kernel contains a null pointer dereference in the ethtool PHY handling code when a PHY driver is unbound via sysfs. After the unbind operation, the driver pointer becomes null while the PHY device remains attached to the network device. When an ETHTOOL_MSG_PHY_GET request is processed, the code attempts to duplicate the driver name from the null pointer, causing a kernel oops. Based on the description, it can be inferred that any user with write permissions to the unbind file could potentially trigger the vulnerability leading to a crash. This is a classic CWE‑476 null pointer dereference that results in a system crash for any user able to trigger the unbind operation.
Affected Systems
All Linux kernel variants that expose the ethtool PHY handling code to sysfs and allow a driver to be unbound through the /sys/bus/mdio_bus/drivers/<phy_drv>/unbind interface are potentially affected. The patch commit identifiers are listed in the references, but no specific kernel version is named in the data, so any kernel still containing the described bug and enabling the unbind operation may be vulnerable.
Risk and Exploitability
The CVSS score of 5.5 points to a medium severity vulnerability. The EPSS score of <1% indicates a very low likelihood of exploitation at the time of analysis. The vulnerability is not listed in the CISA KEV catalog. Exploitation requires local privileged access to write to the unbind file in sysfs; no remote or local privilege escalation vector is described. The impact is a denial of service due to a kernel crash, but overall risk is low because of the low exploit probability.
OpenCVE Enrichment
Ubuntu USN