GPU VulnDB

Database/AI/ML frameworks & serving

llama.cpp: crafted GGUF tensor offsets read memory outside the mapped model file

CVSS 6.9CVE-2024-58399AI/ML frameworks & servingcurated

Impact

llama_model_loader accepts arbitrary 64-bit tensor offsets from a GGUF file without bounding them against the mapping, so a crafted or truncated model file makes the loader read outside the mapped region. The process either crashes or loads adjacent process memory as model weights - meaning whatever else that address space held can be surfaced through generated output. On a shared inference host that loads tenant-supplied models, this is a path from uploading a model file to disclosing in-process memory. The fix is old (build b2731); the CVE is new, so fleets pinned to a pre-b2731 llama.cpp are the exposure.

Who can reach it

Local with user interaction: an operator or service must load the attacker-supplied GGUF file. The realistic path is a tenant or pipeline that can place model files where llama.cpp will open them.

What to do

Move to llama.cpp build b2731 or later (fix commit 0ead1f10) and restart the processes that load models. If the build cannot be moved, restrict model files to trusted sources, since the loader does no bounds checking on offsets.

References

Related entries

All AI/ML frameworks & serving entries

This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.