Answer in brief
CVE-2025-37989 records a Medium severity (CVSS 5.5) vulnerability in net: phy: leds: fix memory leak. 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.
CVSS is 5.5. 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.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:o:debian:debian_linux:11.0:*:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:6.15:rc1:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:6.15:rc2:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:6.15:rc3:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=2e0bc452f4721520502575362a9cd3c1248d2337 <966d6494e2ed9be9052fcd9815afba830896aaf8 || >=2e0bc452f4721520502575362a9cd3c1248d2337 <95bed65cc0eb2a610550abf849a8b94374da80a7 || >=2e0bc452f4721520502575362a9cd3c1248d2337 <663c3da86e807c6c07ed48f911c7526fad6fe1ff || >=2e0bc452f4721520502575362a9cd3c1248d2337 <f41f097f68a33d392579885426d0734a81219501 || >=2e0bc452f4721520502575362a9cd3c1248d2337 <618541a6cc1511064dfa58c89b3445e21844092f || >=2e0bc452f4721520502575362a9cd3c1248d2337 <41143e71052a00d654c15dc924fda50c1e7357d0 || >=2e0bc452f4721520502575362a9cd3c1248d2337 <7f3d5880800f962c347777c4f8358f29f5fc403c || >=2e0bc452f4721520502575362a9cd3c1248d2337 <b7f0ee992adf601aa00c252418266177eb7ac2bc | 966d6494e2ed9be9052fcd9815afba830896aaf8, 95bed65cc0eb2a610550abf849a8b94374da80a7, 663c3da86e807c6c07ed48f911c7526fad6fe1ff, f41f097f68a33d392579885426d0734a81219501, 618541a6cc1511064dfa58c89b3445e21844092f, 41143e71052a00d654c15dc924fda50c1e7357d0, 7f3d5880800f962c347777c4f8358f29f5fc403c, b7f0ee992adf601aa00c252418266177eb7ac2bc |
| Linux/Linuxgeneric | 4.10 | Not reported |
Published upstream
May 20, 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: leds: fix memory leak A network restart test on a router led to an out-of-memory condition, which was traced to a memory leak in the PHY LED trigger code. The root cause is misuse of the devm API. The registration function (phy_led_triggers_register) is called from phy_attach_direct, not phy_probe, and the unregister function (phy_led_triggers_unregister) is called from phy_detach, not phy_remove. This means the register and unregister functions can be called multiple times for the same PHY device, but devm-allocated memory is not freed until the driver is unbound. This also prevents kmemleak from detecting the leak, as the devm API internally stores the allocated pointer. Fix this by replacing devm_kzalloc/devm_kcalloc with standard kzalloc/kcalloc, and add the corresponding kfree calls in the unregister path.
Quoted source text, attributed separately from HOL analysis.