CVE-2025-53630
BaseFortify
Publication date: 2025-07-10
Last updated on: 2025-07-15
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| ggml | llama.cpp | * |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-122 | A heap overflow condition is a buffer overflow, where the buffer that can be overwritten is allocated in the heap portion of memory, generally meaning that the buffer was allocated using a routine such as malloc(). |
| CWE-680 | The product performs a calculation to determine how much memory to allocate, but an integer overflow can occur that causes less memory to be allocated than expected, leading to a buffer overflow. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is an Integer Overflow in the gguf_init_from_file_impl function within the ggml/src/gguf.cpp file of llama.cpp, which is a C/C++ implementation for inference of several large language models (LLMs). The integer overflow can cause a Heap Out-of-Bounds Read or Write, potentially leading to memory corruption or crashes. This issue has been fixed in a specific commit.
How can this vulnerability impact me? :
The vulnerability can lead to Heap Out-of-Bounds Read or Write, which may cause application crashes, memory corruption, or potentially allow an attacker to execute arbitrary code or cause denial of service when processing malicious input files.
What immediate steps should I take to mitigate this vulnerability?
Update llama.cpp to include the fix from commit 26a48ad699d50b6268900062661bd22f3e792579, which addresses the integer overflow in ggml/src/gguf.cpp. Until the update is applied, avoid processing untrusted input with the vulnerable function to reduce risk.