llama.cpp builds b1886 through b7445 contain a race condition use-after-free vulnerability in the LLaMA-Android JNI wrapper where bench_1model() and free_1context() lack synchronization, allowing Thread A to operate on freed memory while Thread B concurrently frees the llama_context. Attackers can exploit this by performing heap spray with attacker-controlled data containing a fake vtable to hijack the vtable pointer at offset +0x30, causing llama_batch_allocr::clear() to dereference arbitrary memory and achieve remote code execution.
Fix
Patch, vendor advisory and mitigation references on NVD 3
- https://github.com/Vladimir-tokarev-cyera/llama-cpp-security-patches Patch, Third Party Advisory
- https://github.com/ggml-org/llama.cpp/commit/5c0d18881e0e9794c96b2602736b758bac9d9388 Patch
- https://github.com/ggml-org/llama.cpp/releases/tag/b7446 Patch, Release Notes, Vendor Advisory
Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.
Change history 1
- First seenCVSS 7.3 · ggmlNVD modified 2026-10-23 21:10
Affected (CPE criteria) 1
cpe:2.3:a:ggml:llama.cpp:*:*:*:*:*:*:*:*
References 4
- https://github.com/Vladimir-tokarev-cyera/llama-cpp-security-patches Patch, Third Party Advisory
- https://github.com/ggml-org/llama.cpp/commit/5c0d18881e0e9794c96b2602736b758bac9d9388 Patch
- https://github.com/ggml-org/llama.cpp/releases/tag/b7446 Patch, Release Notes, Vendor Advisory
- https://www.vulncheck.com/advisories/llama-cpp-b1886-b7445-race-condition-use-after-free-via-llama-android-cpp Exploit, Third Party Advisory