The issue is related to a double free vulnerability in the pool series allocator, specifically due to the lack of loop checks in the `pool free` function. This can lead to remote code execution in some cases. The vulnerability is caused by the `pool free` function not performing pointer destruction, resulting in Use-After-Free (UAF) vulnerabilities. Arbitrary address writing, combined with other legitimate or illegitimate operations of programs using this library, can lead to remote code execution.