GPU VulnDB

Database/AI/ML frameworks & serving

llama.cpp rpc-server: unauthenticated stack overflow in the ggml-rpc RDMA receive path

CVSS 9.2CVE-2026-118375AI/ML frameworks & servingcurated

Impact

A peer that advertises RDMA capability in the HELLO message can push up to 256 KiB into a one-byte stack variable in rpc_serve_client(), overflowing the rpc-server stack. The record describes a crash with potential code execution. ggml-rpc is how llama.cpp shards a model across machines, so rpc-server listens on the fabric with no authentication of its own and its exposure scales with how many GPU nodes participate in a distributed inference job. Code execution in rpc-server lands in a process that holds GPU contexts and the model weights for that shard; a crash alone takes down every inference request spread across that worker. The RDMA transport makes this reachable over the same RoCE/InfiniBand fabric that crosses tenants in many clusters.

Who can reach it

Anyone able to open a ggml-rpc connection to the rpc-server port, including over the RDMA fabric. No authentication is required - ggml-rpc has none.

What to do

Upgrade to llama.cpp b11865 or later and restart every rpc-server process; affected builds are b8841 through b11864. Where upgrading has to wait, stop exposing rpc-server beyond a trusted network segment - it is designed for a closed network and should never be reachable from tenant pods. Restarting rpc-server kills in-flight distributed inference but needs no node reboot.

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.