CVE-2025-40120: net: usb: asix: hold PM usage ref to avoid PM/MDIO + RTNL deadlock
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.22% (FIRST EPSS).
- Fixed version: Linux Linux 1534517300e12f2930b6ff477b8820ff658afd11, 3d3c4cd5c62f24bb3cb4511b7a95df707635e00a, 3e96cd27ff1a004d84908c1b6cc68ac60913874e.
Low priority for now. Upgrade to Linux Linux 1534517300e12f2930b6ff477b8820ff658afd11, 3d3c4cd5c62f24bb3cb4511b7a95df707635e00a, 3e96cd27ff1a004d84908c1b6cc68ac60913874e or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Nov 12, 2025
- Updated
- Oct 19, 2026
- EPSS
- 0.2% · 12th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 5.14affected
- 4a2c7217cd5a87e85ceb761e307b030fe6db4805 and later · before 71a0ba7fdaf8d035426912a4ed7bf1738a81010caffected · git
- 4a2c7217cd5a87e85ceb761e307b030fe6db4805 and later · before 3e96cd27ff1a004d84908c1b6cc68ac60913874eaffected · git
- 4a2c7217cd5a87e85ceb761e307b030fe6db4805 and later · before 724a9db84188f80ef60b1f21cc7b4e9c84e0cb64affected · git
- 4a2c7217cd5a87e85ceb761e307b030fe6db4805 and later · before 1534517300e12f2930b6ff477b8820ff658afd11affected · git
- 4a2c7217cd5a87e85ceb761e307b030fe6db4805 and later · before 9d8bcaf6fae1bd82bc27ec09a2694497e6f6c4b4affected · git
- 4a2c7217cd5a87e85ceb761e307b030fe6db4805 and later · before 3d3c4cd5c62f24bb3cb4511b7a95df707635e00aaffected · git
- before 5.14not affected · semver
- 5.15.195 and later · up to and including 5.15.*not affected · semver
- 6.1.156 and later · up to and including 6.1.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.158-1 | 6.1.158-1 |
| Debian:13 | linux | before 6.12.57-1 | 6.12.57-1 |
| Debian:14 | linux | before 6.17.6-1 | 6.17.6-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2025-40118Nov 12, 2025 · scsi: pm80xx: Fix array-index-out-of-of-bounds on rmmod31Monitor
- ← EarlierCVE-2025-40119Nov 12, 2025 · ext4: fix potential null deref in ext4_mb_init()0Monitor
- Later →CVE-2025-40121Nov 12, 2025 · ASoC: Intel: bytcr_rt5651: Fix invalid quirk input mapping0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 1534517300e12f2930b6ff477b8820ff658afd11 | Vendor (CNA) |
| Linux Linux | 3d3c4cd5c62f24bb3cb4511b7a95df707635e00a | Vendor (CNA) |
| Linux Linux | 3e96cd27ff1a004d84908c1b6cc68ac60913874e | Vendor (CNA) |
| Linux Linux | 71a0ba7fdaf8d035426912a4ed7bf1738a81010c | Vendor (CNA) |
| Linux Linux | 724a9db84188f80ef60b1f21cc7b4e9c84e0cb64 | Vendor (CNA) |
| Linux Linux | 9d8bcaf6fae1bd82bc27ec09a2694497e6f6c4b4 | Vendor (CNA) |
| debian:linux | 6.1.158-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- git.kernel.org/stable/c/3d3c4cd5c62f24bb3cb4511b7a95df707635e00a
- git.kernel.org/stable/c/3e96cd27ff1a004d84908c1b6cc68ac60913874e
- git.kernel.org/stable/c/71a0ba7fdaf8d035426912a4ed7bf1738a81010c
- git.kernel.org/stable/c/724a9db84188f80ef60b1f21cc7b4e9c84e0cb64
- git.kernel.org/stable/c/9d8bcaf6fae1bd82bc27ec09a2694497e6f6c4b4
Vendor advisories and official records. Exploit/PoC links are deliberately left out.