Radare2: Stack-use-after-return in check_buffer
A stack-use-after-return vulnerability has been identified in the check_buffer function of radare2, as reported by OSS-Fuzz. This issue involves reading memory after the stack frame has been returned, which can lead to undefined behavior. The vulnerability affects multiple specific versions of radare2 from 5.8.0 through 6.2.0 and a commit identified by hash 67ead854ea3736384f6d13a56ce9e5fa14c9478c. There is no CVSS score available, and no known exploits in the wild have been reported. The severity is assessed as medium based on the nature of the vulnerability and available information. No patch or remediation details are provided in the source data.
AI Analysis
Technical Summary
The OSS-Fuzz project reported a stack-use-after-return vulnerability in radare2's check_buffer function. The crash involves reading memory after the stack frame has been returned, specifically in the call stack involving check_buffer, r_bin_get_binplugin_by_buffer, and r_bin_file_new_from_buffer. This vulnerability affects multiple exact versions of radare2 from 5.8.0 to 6.2.0 and a specific commit hash. No CVSS score or vendor advisory is provided, and no known exploits are reported.
Potential Impact
The vulnerability can cause a stack-use-after-return memory error, which may lead to undefined behavior such as crashes or potential memory corruption. No direct evidence of exploitation or broader impact is available from the provided data.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Since no patch or fix information is provided, users should monitor official radare2 channels for updates addressing this issue.
Radare2: Stack-use-after-return in check_buffer
Description
A stack-use-after-return vulnerability has been identified in the check_buffer function of radare2, as reported by OSS-Fuzz. This issue involves reading memory after the stack frame has been returned, which can lead to undefined behavior. The vulnerability affects multiple specific versions of radare2 from 5.8.0 through 6.2.0 and a commit identified by hash 67ead854ea3736384f6d13a56ce9e5fa14c9478c. There is no CVSS score available, and no known exploits in the wild have been reported. The severity is assessed as medium based on the nature of the vulnerability and available information. No patch or remediation details are provided in the source data.
Affected software
pkg:generic/radare2Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The OSS-Fuzz project reported a stack-use-after-return vulnerability in radare2's check_buffer function. The crash involves reading memory after the stack frame has been returned, specifically in the call stack involving check_buffer, r_bin_get_binplugin_by_buffer, and r_bin_file_new_from_buffer. This vulnerability affects multiple exact versions of radare2 from 5.8.0 to 6.2.0 and a specific commit hash. No CVSS score or vendor advisory is provided, and no known exploits are reported.
Potential Impact
The vulnerability can cause a stack-use-after-return memory error, which may lead to undefined behavior such as crashes or potential memory corruption. No direct evidence of exploitation or broader impact is available from the provided data.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Since no patch or fix information is provided, users should monitor official radare2 channels for updates addressing this issue.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- OSV-2022-993
- Osv Schema Version
- 1.3.0
- Ecosystems
- ["OSS-Fuzz"]
Threat ID: 6a7891debf8831d539c87a15
Added to database: 08/09/2026, 14:42:38 UTC
Last enriched: 09/07/2026, 17:04:08 UTC
Last updated: 09/22/2026, 08:37:41 UTC
Views: 56
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.