Radare2 Use-After-Free Vulnerability in GDB Client (CVE-2026-8696)
Radare2 version 6.1.5 contains a use-after-free vulnerability (CVE-2026-8696) in the gdbr_pids_list() function, allowing remote attackers to cause a denial of service or potentially execute arbitrary code via malformed thread information responses.
Radare2 is susceptible to a use-after-free vulnerability, CVE-2026-8696, present in version 6.1.5. The flaw resides within the gdbr_pids_list() function of the GDB client core. Remote attackers can exploit this vulnerability by transmitting crafted thread information responses. Successful exploitation can lead to a denial-of-service condition or, potentially, the execution of arbitrary code on the affected system. The root cause is identified as double-free memory corruption, which occurs during the cleanup process when qsThreadInfo fails after qfThreadInfo successfully allocates RDebugPid structures. This poses a significant risk to systems utilizing Radare2 for debugging or reverse engineering purposes, as a malicious actor could disrupt operations or gain unauthorized control.
Attack Chain
- Attacker establishes a connection to the Radare2 GDB server.
- Attacker sends a
qfThreadInfocommand to request thread information. - The
qfThreadInfofunction in Radare2 allocates memory forRDebugPidstructures. - Attacker sends a crafted response designed to cause
qsThreadInfoto fail. qsThreadInfofails to process the malformed thread information response.- The error handling path attempts to clean up the allocated
RDebugPidstructures. - Due to a flaw in the cleanup logic, the same memory is freed twice, triggering a double-free condition.
- The use-after-free vulnerability is triggered, leading to a denial-of-service or potential arbitrary code execution.
Impact
Successful exploitation of this vulnerability (CVE-2026-8696) can result in a denial-of-service condition, rendering the Radare2 instance unusable. In a more severe scenario, attackers might be able to leverage the memory corruption to execute arbitrary code on the affected system, potentially gaining complete control. The impact is primarily on systems using Radare2 for debugging, reverse engineering, and analysis. This could impact software development, security research, and incident response activities.
Recommendation
- Upgrade to a patched version of Radare2 that addresses CVE-2026-8696 as soon as a patch is available.
- Deploy the Sigma rules provided below to detect potential exploitation attempts targeting CVE-2026-8696.
- Monitor network traffic for malformed GDB thread information responses using the
network_connectionSigma rule to identify potential exploitation attempts. - Enable process creation logging on systems running Radare2 to facilitate detection of malicious activities using the
process_creationSigma rule.
Detection coverage 2
Detects CVE-2026-8696 Exploitation - Radare2 GDB Malformed Thread Info Response
highDetects CVE-2026-8696 exploitation - monitors network connections for GDB traffic and flags connections with excessively large data transfers immediately following thread info requests, which may indicate an attempt to trigger the use-after-free vulnerability.
Detects CVE-2026-8696 Exploitation - Radare2 Suspicious Process Creation
mediumDetects CVE-2026-8696 exploitation - identifies unusual child processes spawned by Radare2, potentially indicating successful code execution via the use-after-free.
Detection queries are available on the platform. Get full rules →