CVE-2025-60360 identifies a memory leak vulnerability in radare2, an open-source reverse engineering tool widely used for binary analysis and debugging. The flaw exists in the function r2r_subprocess_init in versions 5.9.8 and earlier. A memory leak occurs when allocated memory is not properly released, causing gradual consumption of system memory over time. Although this vulnerability does not directly allow code execution or privilege escalation, continuous exploitation could exhaust system resources, leading to degraded performance or denial of service (DoS). The absence of a CVSS score and known exploits suggests it is not currently exploited in the wild, but the vulnerability remains a concern for environments where radare2 is heavily used. The lack of patch links indicates that a fix may not yet be publicly available, emphasizing the need for vigilance. Since radare2 is often employed by security researchers and developers, the vulnerability could impact the stability of analysis environments, especially when processing untrusted or malformed binaries. The technical details do not indicate any authentication or user interaction requirements, implying that any user with access to the vulnerable radare2 instance could trigger the leak. However, exploitation requires deliberate invocation of the affected function, limiting the attack surface to users running the tool.

For European organizations, the primary impact of CVE-2025-60360 is potential resource exhaustion leading to denial of service conditions on systems running vulnerable radare2 versions. This could disrupt software analysis workflows, delay security research, and impact development pipelines relying on reverse engineering. While confidentiality and integrity are not directly compromised, availability degradation can affect operational efficiency and incident response capabilities. Organizations using radare2 in automated or large-scale analysis environments may experience amplified effects due to repeated triggering of the memory leak. The vulnerability could also increase operational costs by requiring more frequent system restarts or memory management interventions. Given radare2's niche but critical role in cybersecurity and software development, the impact is significant within those contexts but limited outside them.

To mitigate CVE-2025-60360, organizations should first monitor official radare2 repositories and security advisories for patches addressing the memory leak. Until a patch is available, users should limit the use of vulnerable radare2 versions, especially in automated or high-load environments. Employing resource monitoring tools to detect abnormal memory consumption during radare2 operations can help identify exploitation attempts. Running radare2 with restricted privileges and isolating it within containerized or sandboxed environments can minimize potential impact. Additionally, avoid processing untrusted or malformed binaries that could trigger the leak. Organizations should also consider alternative reverse engineering tools if immediate patching is not feasible. Finally, integrating memory leak detection tools during development and testing phases can prevent similar vulnerabilities in custom tooling.