CVE-2025-38537net: phy: Don't register LEDs for genphy
- 5.5MediumCVSS base score
- 0.18%Exploitation in 30 daysEPSS · top 93% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
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.
Timeline
ID reserved
By Linux
- 4 months later
· 4 months later
Published
- 15 months later
· 15 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| NVDNVD · Analyzed | 3.1 | Medium5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
- EPSS (exploitation in 30 days)
- 0.18% · top 93% of all CVEs (17 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: partial
The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.
Affected products
- affected 01e5b728e9e43ae444e0369695a5f72209906464 – < ec158d05eaa91b2809cab65f8068290e3c05ebdd
- affected 01e5b728e9e43ae444e0369695a5f72209906464 – < fd6493533af9e5d73d0d42ff2a8ded978a701dc6
- affected 01e5b728e9e43ae444e0369695a5f72209906464 – < 75e1b2079ef0653a2f7aa69be515d86b7faf1908
- affected 01e5b728e9e43ae444e0369695a5f72209906464 – < f0f2b992d8185a0366be951685e08643aae17d6d
- affected 6.4
- unaffected < 6.4
- unaffected 6.6.100 – ≤ 6.6.*
- unaffected 6.12.40 – ≤ 6.12.*
- unaffected 6.15.8 – ≤ 6.15.*
- unaffected 6.16 – ≤ *
References
References4
- https://git.kernel.org/stable/c/ec158d05eaa91b2809cab65f8068290e3c05ebdd (opens in a new tab)
- https://git.kernel.org/stable/c/fd6493533af9e5d73d0d42ff2a8ded978a701dc6 (opens in a new tab)
- https://git.kernel.org/stable/c/75e1b2079ef0653a2f7aa69be515d86b7faf1908 (opens in a new tab)
- https://git.kernel.org/stable/c/f0f2b992d8185a0366be951685e08643aae17d6d (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2025-27891 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2025-38537)Record last updated .