# CVE-2025-5641: Radare2 radiff2 cons.c r_cons_is_breaked memory corruption

> Local attackers can trigger memory corruption in Radare2's radiff2 via the experimental -T flag, potentially causing crashes or code execution.

- **Severity:** Low 2.0 (`CVSS:4.0/AV:L/AC:H/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 5 Jun 2025
- **Updated:** 5 Jun 2025
- **Also known as:** GHSA-mrww-q696-jcq2, UBUNTU-CVE-2025-5641

## What is CVE-2025-5641?

CVE-2025-5641 is a low-severity memory corruption vulnerability in Radare Radare2, published on 5 Jun 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability was found in Radare2 5.9.9. It has been rated as problematic. This issue affects the function r_cons_is_breaked in the library /libr/cons/cons.c of the component radiff2. The manipulation of the argument -T leads to memory corruption. It is possible to launch the attack on the local host. The complexity of an attack is rather high. The exploitation is known to be difficult. The exploit has been disclosed to the public and may be used. The real existence of this vulnerability is still doubted at the moment. The identifier of the patch is 5705d99cc1f23f36f9a84aab26d1724010b97798. It is recommended to apply a patch to fix this issue. The documentation explains that the parameter -T is experimental and "crashy". Further analysis has shown "the race is not a real problem unless you use asan". An additional warning regarding threading support has been added.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2025-5641?

It affects 1 product.


Products: Radare Radare2.

## How do I fix CVE-2025-5641?

Apply the vendor's patch.

## Is CVE-2025-5641 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-5641 exists.

## Other vulnerabilities in Radare Radare2

- [CVE-2025-1864](https://insights.sbomify.com/CVE-2025-1864/): Buffer Overflow and Potential Code Execution in Radare2 (critical 10.0)
- [CVE-2025-1744](https://insights.sbomify.com/CVE-2025-1744/): Out-of-bounds Write in radare2 (critical 10.0)
- [CVE-2021-32494](https://insights.sbomify.com/CVE-2021-32494/): Denial of service in radare2 (critical 10.0)
- [CVE-2021-32495](https://insights.sbomify.com/CVE-2021-32495/): Use after free in radare2 (critical 10.0)
- [CVE-2024-29646](https://insights.sbomify.com/CVE-2024-29646/): Memory corruption in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-5641 and fix it if it is affected.

What it is: CVE-2025-5641 is a low-severity memory corruption vulnerability in Radare Radare2, published on 5 Jun 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-5641 exists.

Affected product: Radare Radare2. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-5641/ (Markdown: https://insights.sbomify.com/CVE-2025-5641/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-5641
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-5641
- OSV: https://osv.dev/vulnerability/CVE-2025-5641

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-5641/
Summaries are generated and may contain mistakes; the official description above is the record.