A double-free condition occurs during the cleanup of temporary image files, which can be exploited to achieve memory corruption and potentially arbitrary code execution.
The product calls free() twice on the same memory address, potentially leading to modification of unexpected memory locations.