Double-free race condition in crossbeam-channel Channel Drop
CVE-2025-4574 affects the Rust crossbeam-channel crate. According to the provided content, the internal Channel type's Drop method contains a race condition that can, under some circumstances, trigger a double-free. This memory-management flaw can lead to memory corruption during object destruction when concurrent conditions cause the same memory to be freed more than once.
Are you exposed to this one?
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.
Impact, mitigation & remediation
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Mitigation
If you can’t patch tonight, do this now.
Channel type. Where feasible, pin to a known-safe version once identified and monitor upstream for patched releases. No complete mitigation is confirmed in the provided information short of applying the fix.Remediation
Patch, then assume compromise.
Exploits
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Recent activity
14 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
The version that knows your environment.
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.