As noted in undefined behavior 179 of Annex J of the C standard [ISO/IEC 9899:2011], the behavior of a program is undefined when
the pointer argument to the
free
orrealloc
function does not match a pointer earlier returned by a memory management function, or the space has been deallocated by a call tofree
orrealloc
.
Freeing memory that is not allocated dynamically can lead to serious errors similar to those discussed in MEM31-C. Free dynamically allocated memory exactly once. The specific consequences of this error depend on the implementation, but they range from nothing to abnormal program termination. Regardless of the implementation, avoid calling free()
on anything other than a pointer returned by a dynamic-memory allocation function, such as malloc()
, calloc()
, realloc()
, or aligned_alloc
.
...
Tool | Version | Checker | Description | ||||||
---|---|---|---|---|---|---|---|---|---|
| 483 S | Fully implemented. | |||||||
| BAD_FREE | Identifies calls to | |||||||
| FNH.MIGHT | ||||||||
Compass/ROSE | Can detect some violations of this rule. |
...
MITRE CWE: CWE-590, "Free of invalid pointer not on the heap"
Bibliography
[Seacord 2005] Chapter 4, "Dynamic Memory Management"
...