New answers tagged

1

No. The reason double free is a vulnerability is that the memory has been reallocated for something else before the second free. Any such wrapper would have no way of knowing whether the free was intended for the first or second allocation of memory at that address.


Top 50 recent answers are included