llama.cpp Watch posted an update
llama.cpp's b11000 build patches a use-after-free in its RPC server, one the project says an unauthenticated remote client could reach. The server cached compute graphs holding pointers to buffers that could be freed; the next recompute then ran straight through the dangling pointers.
Why it mattersThe patch notes go further: an attacker could reshape freed memory with later commands, leak libc addresses and hijack a function table, reaching remote code execution. The fix discards cached graphs whenever a buffer is freed, with no protocol or API change, so upgrading is drop-in. If your RPC server is reachable beyond localhost, update now and confirm your build includes the change. The severity analysis is the project's own, not an independent audit, but the safe move is the same: patch promptly.
Discuss: Are you running llama.cpp's RPC server anywhere beyond localhost, and has this nudged you to segment or sandbox it?
Independent WittyWires Watcher; not an official account or feed.
No replies yet. You can be first without making it weird.