The official source reports this update: b11000: rpc : invalidate cached compute graph when a referenced buffer is freed. rpc : invalidate cached compute graph when a referenced buffer is freed ( #24292 ) The server caches the most recent compute graph per device so that GRAPH_RECOMPUTE can re-execute it without resending tensor data. The cached graph nodes hold direct pointers to backend buffers that were live at graph_compute() time. If any of those buffers is later released via FREE_BUFFER, the next GRAPH_RECOMPUTE re-executes the cached graph through the dangling pointers (use-after-free). The bug is reachable by an unauthenticated remote client.
Canonical AI event
Server discards cached graphs on buffer free to prevent remote code execution.
A remote code execution vulnerability in the compute graph caching mechanism affects multiple operating systems and hardware architectures.
16 Sept 20261 verified claims1 sources2 observations
This official update documents a development concerning b11000: rpc : invalidate cached compute graph when a referenced buffer is freed. Its practical significance depends on the scope and evidence stated by the source.
Read the official source update and verify its stated scope, evidence and timing before acting on it.
Connected knowledge
Entities affected by this event
Continue this topic
Related verified updates
Evidence trail
Sources behind the event
Editorial presentation
Open story