Local crash via threaded double-free race
Published Jun 5, 2025 · Updated Jun 5, 2025
Double-free in radiff2 5.9.9 allows local users to crash the process by running threaded binary comparisons with the experimental -T option. Concurrent radiff2 worker threads call r_cons_context_break_pop on the same console-break context, causing both threads to free one allocation. Reproduction requires a local command-line invocation and an AddressSanitizer build; the maintainer disputes that the race affects ordinary builds.
Summary
What happened
Double-free in radiff2 5.9.9 allows local users to crash the process by running threaded binary comparisons with the experimental -T option. Concurrent radiff2 worker threads call r_cons_context_break_pop on the same console-break context, causing both threads to free one allocation. Reproduction requires a local command-line invocation and an AddressSanitizer build; the maintainer disputes that the race affects ordinary builds.
The record
- CVE
- CVE-2025-5647
- Published
- Jun 5, 2025
- Updated
- Jun 5, 2025
- Vendor
- radareorg
- Product
- radare2
- Classifications
- CWE-119
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 5, 2025CVE publishedPublication date reported by the CVE source.
- Jun 5, 2025Record 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=5.9.9
What conditions does exploitation require?
What is affected?
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
- radiff2 -T AddressSanitizer double-free proof of conceptproof of concept · demonstrated
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