CVE-2025-39925 is a reference-release flaw in the Linux kernel CAN J1939 subsystem. When a J1939 socket is bound, j1939_sk_bind() acquires an additional reference to struct j1939_priv. The subsystem lacked a NETDEV_UNREGISTER notification handler to release that reference when the associated network device was unregistered. Consequently, the net_device usage count cannot fall sufficiently for unregister_netdevice() to complete. The fix implements NETDEV_UNREGISTER handling that calls j1939_priv_put() to undo the bind-time reference acquisition before socket destruction.
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.
20 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A Linux kernel CAN J1939 vulnerability addressed by implementing a NETDEV_UNREGISTER notification handler.
A Linux kernel CAN J1939 vulnerability addressed by implementing a NETDEV_UNREGISTER notification handler.
A Linux kernel CAN J1939 vulnerability related to missing or improper NETDEV_UNREGISTER notification handling.
A Linux kernel CAN J1939 vulnerability related to missing or improper NETDEV_UNREGISTER notification handling.
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.