CVE-2025-40120net: usb: asix: hold PM usage ref to avoid PM/MDIO + RTNL deadlock
- —Not scoredno CVSS score yet
- 0.22%Exploitation in 30 daysEPSS · top 87% 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: 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.
Timeline
ID reserved
By Linux
- 7 months later
· 7 months later
Published
- 6 months later
· 6 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
No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Deferred.
- EPSS (exploitation in 30 days)
- 0.22% · top 87% of all CVEs (17 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.
Affected products
- affected 4a2c7217cd5a87e85ceb761e307b030fe6db4805 – < 71a0ba7fdaf8d035426912a4ed7bf1738a81010c
- affected 4a2c7217cd5a87e85ceb761e307b030fe6db4805 – < 3e96cd27ff1a004d84908c1b6cc68ac60913874e
- affected 4a2c7217cd5a87e85ceb761e307b030fe6db4805 – < 724a9db84188f80ef60b1f21cc7b4e9c84e0cb64
- affected 4a2c7217cd5a87e85ceb761e307b030fe6db4805 – < 1534517300e12f2930b6ff477b8820ff658afd11
- affected 4a2c7217cd5a87e85ceb761e307b030fe6db4805 – < 9d8bcaf6fae1bd82bc27ec09a2694497e6f6c4b4
- affected 4a2c7217cd5a87e85ceb761e307b030fe6db4805 – < 3d3c4cd5c62f24bb3cb4511b7a95df707635e00a
- affected 5.14
- unaffected < 5.14
- unaffected 5.15.195 – ≤ 5.15.*
- unaffected 6.1.156 – ≤ 6.1.*
- unaffected 6.6.112 – ≤ 6.6.*
- unaffected 6.12.53 – ≤ 6.12.*
- unaffected 6.17.3 – ≤ 6.17.*
- unaffected 6.18 – ≤ *
References
References6
- https://git.kernel.org/stable/c/71a0ba7fdaf8d035426912a4ed7bf1738a81010c (opens in a new tab)
- https://git.kernel.org/stable/c/3e96cd27ff1a004d84908c1b6cc68ac60913874e (opens in a new tab)
- https://git.kernel.org/stable/c/724a9db84188f80ef60b1f21cc7b4e9c84e0cb64 (opens in a new tab)
- https://git.kernel.org/stable/c/1534517300e12f2930b6ff477b8820ff658afd11 (opens in a new tab)
- https://git.kernel.org/stable/c/9d8bcaf6fae1bd82bc27ec09a2694497e6f6c4b4 (opens in a new tab)
- https://git.kernel.org/stable/c/3d3c4cd5c62f24bb3cb4511b7a95df707635e00a (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-124963 (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-40120)Record last updated .