CVE-2025-40120
net: usb: asix: hold PM usage ref to avoid PM/MDIO + RTNL deadlock
Reported by linux · Published November 12, 2025
In the Linux kernel, the following vulnerability has been resolved: net: usb: asix: hold PM usage ref to avoid PM/MDIO + RTNL deadlock Prevent USB runtime PM (autosuspend) for AX88772* in bind. usbnet enables runtime PM (autosuspend) by default, so disabling it via the usb_driver flag is ineffective. On AX88772B, autosuspend shows no measurable power saving with current driver (no link partner, admin up/down). The ~0.453 W -> ~0.248 W drop on v6.1 comes from phylib powering the PHY off on admin-down, not from USB autosuspend. The real hazard is that with runtime PM enabled, ndo_open() (under RTNL) may synchronously trigger autoresume (usb_autopm_get_interface()) into asix_resume() while the USB PM lock is held. Resume paths then invoke phylink/phylib and MDIO, which also expect RTNL, leading to possible deadlocks or PM lock vs MDIO wake issues. To avoid this, keep the device runtime-PM active by taking a usage reference in ax88772_bind() and dropping it in unbind(). A non-zero PM usage count blocks runtime suspend regardless of userspace policy (.../power/control - pm_runtime_allow/forbid), making this approach robust against sysfs overrides. Holding a runtime-PM usage ref does not affect system-wide suspend; system sleep/resume callbacks continue to run as before.
EPSS 0.22% · 12.7th percentile
Fixed versions
Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.
| Package | Ecosystem | Fixed in |
|---|---|---|
| Linux | Linux | 9d8bcaf6fae1bd82bc27ec09a2694497e6f6c4b4, 724a9db84188f80ef60b1f21cc7b4e9c84e0cb64, 71a0ba7fdaf8d035426912a4ed7bf1738a81010c, 5.14, 3e96cd27ff1a004d84908c1b6cc68ac60913874e, 1534517300e12f2930b6ff477b8820ff658afd11 |
Risk scores
Affected products
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | 4a2c7217cd5a87e85ceb761e307b030fe6db4805, 4a2c7217cd5a87e85ceb761e307b030fe6db4805, 4a2c7217cd5a87e85ceb761e307b030fe6db4805 |
| Linux | Linux | 5.14, 0, 5.15.195 |
| Linux | Linux | 6.1.156, 6.12.53, 6.17.3 |
| linux | linux_kernel | 5.14, 5.14, 5.14 |
Timeline
- Oct 12, 2025 PoC Published (12 in total, the first dated here)
- Nov 11, 2025 CVE Published
- Nov 12, 2025 EPSS Score (30 in total, the first dated here)
- Mar 29, 2026 Distribution Patch (194 in total, the first dated here)
- Mar 29, 2026 Security Advisory (201 in total, the first dated here)
- May 11, 2026 CVE Updated
- Jun 8, 2026 Coalition ESS Score
Query this with the API
The same record, from the CLI:
vulnetix vdb vuln CVE-2025-40120
vulnetix vdb fixes CVE-2025-40120
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-40120/fixes/registry"
The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart