In this code, x is freed twice. What is the risk of this code? x = malloc(200); /* do something with x / free(x); / do something else */ free(x);
This is a double free vulnerability and must be fixed
The second call to free() will return an error
There might be compiler warnings, but the program will run fine
This is not a security issue