[openssl-dev] [openssl.org #4401] [PATCH] plug potential memory leak(s) in OpenSSL 1.1 pre 4 in 'ec_lib.c'

[Richard Moore]

On 9 March 2016 at 05:30, Peter Waltenberg <pwalten at au1.ibm.com> wrote:

> No, you got that right, NULL being 'safe' to free varies with OS.
>
>
​It shouldn't if you're programming in C, from the standard (C89):

The free function causes the space pointed to by ptr to be deallocated,
that is, made available for further allocation. If ptr is a null pointer,
no action occurs. Otherwise, if the argument does not match a pointer
earlier returned by the calloc , malloc , or realloc function, or if the
space has been deallocated by a call to free or realloc , the behavior is
undefined.

Cheers

Rich.​
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mta.openssl.org/pipermail/openssl-dev/attachments/20160309/8e9fdf95/attachment-0001.html>