CVE-2025-38537
net: phy: Don't register LEDs for genphy
Reported by linux · Published August 16, 2025
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.
Fixed versions
Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.
| Package | Ecosystem | Fixed in |
|---|---|---|
| kernel6.12-libbpf-static | Amazon Linux | 1:6.12.40-63.114.amzn2023 |
| kernel6.12-modules-extra-common | Amazon Linux | 1:6.12.40-63.114.amzn2023 |
| kernel6.12-tools-devel | Amazon Linux | 1:6.12.40-63.114.amzn2023 |
| kernel6.12 | Amazon Linux | 1:6.12.40-63.114.amzn2023 |
| kernel6.12-libbpf-devel | Amazon Linux | 1:6.12.40-63.114.amzn2023 |
| kernel6.12-tools | Amazon Linux | 1:6.12.40-63.114.amzn2023 |
| kernel6.12-modules-extra | Amazon Linux | 1:6.12.40-63.114.amzn2023 |
| kernel6.12-libbpf | Amazon Linux | 1:6.12.40-63.114.amzn2023 |
| Linux | Linux | ec158d05eaa91b2809cab65f8068290e3c05ebdd, 6.4 |
Affected products
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | 01e5b728e9e43ae444e0369695a5f72209906464, 01e5b728e9e43ae444e0369695a5f72209906464, 01e5b728e9e43ae444e0369695a5f72209906464 |
| Linux | Linux | 6.4, 0, 6.6.100 |
| amazon:2023 | kernel6.12-libbpf-static | 0 |
| amazon:2023 | kernel6.12-modules-extra-common | 0 |
| amazon:2023 | kernel6.12-tools-devel | 0 |
| amazon:2023 | kernel6.12 | 0 |
| amazon:2023 | kernel6.12-libbpf-devel | 0 |
| amazon:2023 | kernel6.12-tools | 0 |
| amazon:2023 | kernel6.12-modules-extra | 0 |
| amazon:2023 | kernel6.12-libbpf | 0 |
| Linux | Linux | 6.16, 01e5b728e9e43ae444e0369695a5f72209906464, 01e5b728e9e43ae444e0369695a5f72209906464 |
| amazon:2023 | kernel6.12-devel | 0 |
| amazon:2023 | perf6.12 | 0 |
| amazon:2023 | kernel6.12-headers | 0 |
| amazon:2023 | kernel-livepatch-6.12.40-63.114 | 0 |
| linux | linux_kernel | 6.4, 6.4, 6.4 |
| amazon:2023 | python3-perf6.12 | 0 |
| amazon:2023 | bpftool6.12 | 0 |
Timeline
- Aug 8, 2025 CVE Published
- Aug 16, 2025 EPSS Score (30 in total, the first dated here)
- Oct 12, 2025 PoC Published (13 in total, the first dated here)
- Mar 29, 2026 Distribution Patch (155 in total, the first dated here)
- Mar 29, 2026 Security Advisory (163 in total, the first dated here)
- Jun 9, 2026 Coalition ESS Score
Query this with the API
The same record, from the CLI:
vulnetix vdb vuln CVE-2025-38537
vulnetix vdb fixes CVE-2025-38537
Or with curl, using the org id and key from your account page:
curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
"https://api.vdb.vulnetix.com/v2/vuln/CVE-2025-38537/fixes/registry"
The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart