Memory corruption via unsynchronized channel cleanup
Published May 13, 2025 · Updated Jun 30, 2026
Double free in Crossbeam Project crossbeam-channel 0.5.12 through 0.5.14 allows attackers to corrupt memory when a channel is dropped. Channel::discard_all_messages can free a non-null head.block without atomically replacing it with null, so Channel::drop frees the pointer again. Triggering requires a difficult concurrency race during channel cleanup; the resulting double free corrupts memory in the consuming process and can interrupt it.
Summary
What happened
Double free in Crossbeam Project crossbeam-channel 0.5.12 through 0.5.14 allows attackers to corrupt memory when a channel is dropped. Channel::discard_all_messages can free a non-null head.block without atomically replacing it with null, so Channel::drop frees the pointer again. Triggering requires a difficult concurrency race during channel cleanup; the resulting double free corrupts memory in the consuming process and can interrupt it.
The record
- CVE
- CVE-2025-4574
- Published
- May 13, 2025
- Updated
- Jun 30, 2026
- Vendor
- 389 Directory Server
- Product
- Red Hat OpenShift AI
- Classifications
- CWE-415, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 13, 2025CVE publishedPublication date reported by the CVE source.
- Jun 30, 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?
Affected versions are unavailable in this record. Check the vendor advisory for version and patch details.
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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.
Weakness, pattern, technique
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