Process crash via mismatched JNI deallocation
Published Aug 6, 2026 · Updated Aug 6, 2026
Double free in the LLaMA-Android JNI wrapper in llama.cpp 0.9.0 through 0.17.1 allows attackers to crash the process locally. The new_1batch() function allocates batch storage with malloc(), but free_1batch() releases the same storage with the incompatible C++ delete operator, corrupting heap metadata. Triggering requires local access and user interaction; allocator state determines whether corruption stops at a crash or permits arbitrary code execution.
Summary
What happened
Double free in the LLaMA-Android JNI wrapper in llama.cpp 0.9.0 through 0.17.1 allows attackers to crash the process locally. The new_1batch() function allocates batch storage with malloc(), but free_1batch() releases the same storage with the incompatible C++ delete operator, corrupting heap metadata. Triggering requires local access and user interaction; allocator state determines whether corruption stops at a crash or permits arbitrary code execution.
The record
- CVE
- CVE-2026-43622
- Published
- Aug 6, 2026
- Updated
- Aug 6, 2026
- Vendor
- Georgi Gerganov
- Product
- llama.cpp
- Classifications
- CWE-762, CWE-415, T1499.004
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 6, 2026CVE publishedPublication date reported by the CVE source.
- Aug 6, 2026Record 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0.9.0 <=0.17.1
- Affected versionversion=b1886 <=b7445
What conditions does exploitation require?
What is affected?
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