A use-after-free issue exists in libcurl, allowing attackers to potentially control which connection is used or have other unspecified impacts. This issue arises when an application uses libcurl's multi interface and an easy handle is added to a multi handle. If `curl multi cleanup()` is called with an easy handle still added to it, a pointer to a freed connection struct can be left dangling in the easy handle. If the easy handle is then used again with `curl easy perform()`, it can blindly use the connection struct pointer now pointing to freed memory, potentially leading to unintended actions. This flaw can be exploited by an application allocating its own fake version of the connection struct and filling in data, causing `curl easy perform()` to perform unintended actions.