Service interruption via leaked PHY LED allocations
Published May 20, 2025 · Updated May 11, 2026
Memory leak in the Linux kernel PHY LED trigger code allows local users to exhaust memory through repeated network restarts. phy_led_triggers_register uses device-managed allocations even though registration and unregistration can repeat without driver unbinding, so detached trigger allocations remain retained. The path requires low-privileged local access and a PHY device using LED triggers; sustained exhaustion can interrupt the system.
Summary
What happened
Memory leak in the Linux kernel PHY LED trigger code allows local users to exhaust memory through repeated network restarts. phy_led_triggers_register uses device-managed allocations even though registration and unregistration can repeat without driver unbinding, so detached trigger allocations remain retained. The path requires low-privileged local access and a PHY device using LED triggers; sustained exhaustion can interrupt the system.
The record
- CVE
- CVE-2025-37989
- Published
- May 20, 2025
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-401
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 20, 2025CVE publishedPublication date reported by the CVE source.
- May 11, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=2e0bc452f4721520502575362a9cd3c1248d2337 <41143e71052a00d654c15dc924fda50c1e7357d0
- Affected versionversion=2e0bc452f4721520502575362a9cd3c1248d2337 <618541a6cc1511064dfa58c89b3445e21844092f
- Affected versionversion=2e0bc452f4721520502575362a9cd3c1248d2337 <663c3da86e807c6c07ed48f911c7526fad6fe1ff
- Affected versionversion=2e0bc452f4721520502575362a9cd3c1248d2337 <7f3d5880800f962c347777c4f8358f29f5fc403c
- Affected versionversion=2e0bc452f4721520502575362a9cd3c1248d2337 <95bed65cc0eb2a610550abf849a8b94374da80a7
- Affected versionversion=2e0bc452f4721520502575362a9cd3c1248d2337 <966d6494e2ed9be9052fcd9815afba830896aaf8
- Affected versionversion=2e0bc452f4721520502575362a9cd3c1248d2337 <b7f0ee992adf601aa00c252418266177eb7ac2bc
- Affected versionversion=2e0bc452f4721520502575362a9cd3c1248d2337 <f41f097f68a33d392579885426d0734a81219501
- Affected versionversion=4.10
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo