CWE-762: Mismatched Memory Management Routines

Description:
The product attempts to return a memory resource to the system, but it calls a release function that is not compatible with the function that was originally used to allocate that resource.

Extended Description:
This weakness can be generally described as mismatching memory management routines, such as: 
                
                   The memory was allocated on the stack (automatically), but it was deallocated using the memory management routine free() (CWE-590), which is intended for explicitly allocated heap memory. 
                   The memory was allocated explicitly using one set of memory management functions, and deallocated using a different set. For example, memory might be allocated with malloc() in C++ instead of the new operator, and then deallocated with the delete operator. 
                
             When the memory management functions are mismatched, the consequences may be as severe as code execution, memory corruption, or program crash. Consequences and ease of exploit will vary depending on the implementation of the routines and the object being managed.

Affected languages: Memory-Unsafe, C, C++
Parent weaknesses: CWE-763, CWE-404

Consequences:
  - Integrity: Modify Memory

Detection methods:
  - Automated Dynamic Analysis: Use tools that are integrated during
	     compilation to insert runtime error-checking mechanisms
	     related to memory safety errors, such as AddressSanitizer
	     (ASan) for C/C++ [REF-1518] or 

Mitigations:
  - [Implementation] Only call matching memory management functions. Do not mix and match routines. For example, when you allocate a buffer with malloc(), dispose of the original pointer with free().
  - [Implementation] Choose a language or tool that provides automatic memory management, or makes manual memory management less error-prone. 
                   For example, glibc in Linux provides protection against free of invalid pointers. 
                   When using Xcode to target OS X or iOS, enable automatic 
  - [Architecture and Design] Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. 
                   For example, glibc in Linux provides protection against free of invalid pointers.
  - [Architecture and Design] Use a language that provides abstractions for memory allocation and deallocation.

Demonstrative examples:
This example allocates a BarObj object using the new operator in C++, however, the programmer then deallocates the object using free(), which may lead to unexpected behavior.
Instead, the programmer should have either created the object with one of the malloc family functions, or else deleted the object with the delete operator.
void foo(){ 
                         BarObj *ptr = new BarObj() 
                            /* do some work with ptr here */ 
                            
                            ... 
                            free(ptr); 
                      }
void foo(){ 
                         BarObj *ptr = new BarObj() 
                            /* do some work with ptr here */ 
                            
                            ... 
                         

In this example, the program does not use matching functions such as malloc/free, new/delete, and new[]/delete[] to allocate/deallocate the resource.

class A { void foo(); }; void A::foo(){ int *ptr; ptr = (int*)malloc(sizeof(int)); delete ptr; }