Local denial of service via leaked buffers
Published Oct 17, 2025 · Updated Oct 17, 2025
Memory leak in radare2 5.9.8 and earlier allows local users to interrupt service by repeatedly invoking bochs_open. Error and completion paths in shlr/bochs/src/libbochs.c return without releasing b->data and lpTmpBuffer. A low-privilege local user must reach the Bochs-opening path; repeated calls consume process memory and can deny availability.
Summary
What happened
Memory leak in radare2 5.9.8 and earlier allows local users to interrupt service by repeatedly invoking bochs_open. Error and completion paths in shlr/bochs/src/libbochs.c return without releasing b->data and lpTmpBuffer. A low-privilege local user must reach the Bochs-opening path; repeated calls consume process memory and can deny availability.
The record
- CVE
- CVE-2025-60361
- Published
- Oct 17, 2025
- Updated
- Oct 17, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-401, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 17, 2025CVE publishedPublication date reported by the CVE source.
- Oct 17, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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
No public exploit references are available in this record.
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