The Linux kernel’s phylink subsystem stored a PHY device pointer before the final, potentially failing step of the bringup sequence. If the last step fails, the PHY is detached and freed, yet the phylink structure still retains the stale pointer. Subsequent operations that read this pointer can access freed memory, causing memory corruption or a kernel crash. The description does not explicitly state who can exploit this flaw, but it is inferred that an entity controlling network interface re‑configuration could potentially provoke the failure and trigger a crash.

The flaw exists in all Linux kernel releases that incorporated the buggy code prior to the referenced commit 4e7a4af364c2048bafb213bf0ef4a89dcbe1bfd4. This includes mainline kernel and any vendor distributions built before that patch was applied. Specific vulnerable firmware versions are not enumerated in the data provided, so any kernel containing the prior code is potentially affected.

Based on the description, it is inferred that an attacker might trigger the failure path by influencing the NIC state, such as re‑configuring the interface or causing link fluctuations. The CVSS score of 4.1 indicates moderate severity, while the EPSS score of less than 1% shows a very low probability of exploitation. The vulnerability involves kernel memory, implying a moderate impact if exploited. It is not listed in the CISA KEV catalog, indicating no known public exploits at this time. The likely attack vector is inferred to be either local or remote access that can influence the NIC state, though the specific condition for exploitation and potential for denial of service are considered inferred.