Kernel hang via inverted phylink lock order
Published Oct 1, 2025 · Updated May 11, 2026
Improper locking in Linux 6.14 through 6.16.7 allows local users to hang the kernel during concurrent phylink state changes. phy_config_inband() acquires phydev->lock beneath state_mutex, reversing the order used by phylink_phy_change() and creating an AB/BA deadlock. Reachability requires a PHY using in-band configuration and overlap between phylink_resolve() and phy_link_up() or phy_link_down(); the consequence is an availability-only deadlock.
Summary
What happened
Improper locking in Linux 6.14 through 6.16.7 allows local users to hang the kernel during concurrent phylink state changes. phy_config_inband() acquires phydev->lock beneath state_mutex, reversing the order used by phylink_phy_change() and creating an AB/BA deadlock. Reachability requires a PHY using in-band configuration and overlap between phylink_resolve() and phy_link_up() or phy_link_down(); the consequence is an availability-only deadlock.
The record
- CVE
- CVE-2025-39915
- Published
- Oct 1, 2025
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-667, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 1, 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=5fd0f1a02e750e2db4038dee60edea669ce5aab1 <052ac41c379c8b87629808be612a482b2d0ae283
- Affected versionversion=5fd0f1a02e750e2db4038dee60edea669ce5aab1 <e2a10daba84968f6b5777d150985fd7d6abc9c84
- Affected versionversion=6.14
What conditions does exploitation require?
What is affected?
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.
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