Loading vulnerability…
CVE-2025-39905 is a race condition in the Linux kernel net/phylink subsystem. phylink_resolve() can run concurrently with phylink_bringup_phy() or phylink_disconnect_phy(), which modify pl->phydev. Although state_mutex is used for serialization, lock-order constraints with phydev->lock require dereferencing pl->phydev before state_mutex can safely be acquired, creating a racy access. The fix adds a dedicated lock to serialize concurrent writes to pl->phydev with the resolver.
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.
4 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A vulnerability addressed by the referenced CentOS/TuxCare security advisory.
A Linux kernel vulnerability in the phylink networking component involving concurrent phydev writes and missing serialization.
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.