Answer in brief
CVE-2025-38537 records a Unknown severity vulnerability in net: phy: Don't register LEDs for genphy. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=01e5b728e9e43ae444e0369695a5f72209906464 <ec158d05eaa91b2809cab65f8068290e3c05ebdd || >=01e5b728e9e43ae444e0369695a5f72209906464 <fd6493533af9e5d73d0d42ff2a8ded978a701dc6 || >=01e5b728e9e43ae444e0369695a5f72209906464 <75e1b2079ef0653a2f7aa69be515d86b7faf1908 || >=01e5b728e9e43ae444e0369695a5f72209906464 <f0f2b992d8185a0366be951685e08643aae17d6d | ec158d05eaa91b2809cab65f8068290e3c05ebdd, fd6493533af9e5d73d0d42ff2a8ded978a701dc6, 75e1b2079ef0653a2f7aa69be515d86b7faf1908, f0f2b992d8185a0366be951685e08643aae17d6d |
| Linux/Linuxgeneric | 6.4 | Not reported |
Published upstream
Aug 16, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Nov 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Nov 5, 2026
In the Linux kernel, the following vulnerability has been resolved: net: phy: Don't register LEDs for genphy If a PHY has no driver, the genphy driver is probed/removed directly in phy_attach/detach. If the PHY's ofnode has an "leds" subnode, then the LEDs will be (un)registered when probing/removing the genphy driver. This could occur if the leds are for a non-generic driver that isn't loaded for whatever reason. Synchronously removing the PHY device in phy_detach leads to the following deadlock: rtnl_lock() ndo_close() ... phy_detach() phy_remove() phy_leds_unregister() led_classdev_unregister() led_trigger_set() netdev_trigger_deactivate() unregister_netdevice_notifier() rtnl_lock() There is a corresponding deadlock on the open/register side of things (and that one is reported by lockdep), but it requires a race while this one is deterministic. Generic PHYs do not support LEDs anyway, so don't bother registering them.
Quoted source text, attributed separately from HOL analysis.