Loading vulnerability…
CVE-2025-39905 is a race condition in the Linux kernel net/phylink subsystem. phylink_resolve() can access the phylink PHY-device pointer while concurrent phylink_bringup_phy() or phylink_disconnect_phy() operations modify that pointer. Although state_mutex is used for synchronization, the required lock ordering with the PHY-device lock means dereferencing the PHY-device pointer before acquiring state_mutex is racy. The fix introduces a dedicated lock to serialize PHY-device pointer writes with resolver activity and avoid the lock inversion issue.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.