Page History

The C Standard, Annex J (184) [ISO/IEC 9899:2024], states that the behavior of a program is undefined when

The pointer argument to the free or realloc function does not match a pointer earlier returned by a memory management function, or the space has been deallocated by a call to free or realloc.

See also undefined behavior 184.

Freeing memory that is not allocated dynamically can lead to result in heap corruption and other serious errors. The specific consequences of this error depends on the compiler, but ranges from nothing to abnormal program termination. Regardless of the compiler, avoid calling free() on non-dynamic memoryDo not call free() on a pointer other than one returned by a standard memory allocation function, such as malloc(), calloc(), realloc(), or aligned_alloc().

A similar situation arises when realloc() is supplied a pointer to non-dynamically allocated memory. The realloc() function is used to resize a block of dynamic memory. If realloc() is supplied a pointer to memory not allocated by a standard memory allocation function, such as{{malloc()}}, the behavior is undefined. One consequence is that the program may also terminate abnormally.

Non-compliant Code Example 1

In this example, a file is opened for reading. If the file is opened successfully, memory is allocated by malloc() and referenced by str. A message indicating that the file was opened properly is copied into the dynamically-allocated memory referenced by str and printed. Afterwards, the memory is deallocted by calling free(). If the file does not open correctly, however, str is set to a string literal. Because str now references memory that was not dynamically allocated, an error will occur when this memory is freed.

This rule does not apply to null pointers. The C Standard guarantees that if free() is passed a null pointer, no action occurs.

Noncompliant Code Example

This noncompliant code example sets c_str to reference either dynamically allocated memory or a statically allocated string literal depending on the value of argc. In either case, c_str is passed as an argument to free(). If anything other than dynamically allocated memory is referenced by c_str, the call to free(c_str) is erroneous.

#include <stdlib.h>
#include <string.h>
#include <stdio.h>
 
enum { MAX_ALLOCATION = 1000 };

int main(int argc, const char *argv[]) {
  char *c_str = NULL;
  size_t len;

  if (argc == 2) {
    len = strlen(argv[1]) + 1;
    if (len > MAX_ALLOCATION) {
      /* Handle error */
    }
    c_

FILE *file = NULL;
char *str  = NULL, *fname="~/config_file";
size_t size = 100;

file = fopen("~/config_file","r");
if (file != NULL) {
  str = (char *)malloc(sizelen);
    if (c_str == NULL) {
  
    /* Handle Allocationerror Error */
    }
   snprintf strcpy(c_str, size, "File %s opened properly", fnameargv[1]);
  printf("LOG: %s\n", str);
}
} else {
    c_str = "ERROR OPENING FILEusage: $>a.exe [string]";
    printf("LOG: %s\n", c_str);
  }
  free(c_str);
  return 0;
}

Compliant Solution

...

In the This compliant solution , the call eliminates the possibility of c_str referencing memory that is not allocated dynamically when passed to free() has been moved inside the conditional statement to ensure that only dynamic memory is freed.:

Code Block
bgColor #ccccff lang c
#include <stdlib.h> #include <string.h> #include <stdio.h>   enum { MAX_ALLOCATION = 1000 }; int main(int argc, const char *argv[]) { char *c_str = NULL; size_t len; if (argc == 2) { len = strlen(argv[1]) + 1; if (len > MAX_ALLOCATION) { /* Handle error */ } c_
Code Block
FILE *file = NULL; char *str = NULL, *fname="~/config_file"; size_t size = 100; file = fopen("~/config_file","r"); if (file != NULL) { str = (char *)malloc(sizelen); if (c_str == NULL) { /* Handle Allocation Errorerror */ } snprintf strcpy(c_str, size, "File %s opened properly", fname); argv[1]); } else { printf("LOG: %s\n", str); free(str); /* only dynamic memory is freed */ } else { str = "ERROR OPENING FILE"; printf("LOG: %s\n", str)"usage: $>a.exe [string]"); return EXIT_FAILURE; } free(c_str); return 0; }

...

Noncompliant Code Example

...

This example attempts to resize the string referenced by buf to make enough room to append the string line. However, once in the function append(), there is no way to determine how buf was allocated. When realloc() is called on buf, since buf does not point to dynamic memory, an error may occur.

(realloc())

In this noncompliant example, the pointer parameter to realloc(), buf, does not refer to dynamically allocated memory:

#include <stdlib.h>
 
enum { BUFSIZE = 256 };
 
void f(void

void append(char *buf, size_t count, size_t size) {
  char *line = " <- THIS IS A LINE"buf[BUFSIZE];
  int line_lenchar *p = strlen(line);

  if ((count + line_len) > size) {
    buf = char *)realloc(buf,count+line_len 2 * BUFSIZE);
  if (p size == count + line_len;NULL) {
  }
  strncat(buf,line,line_len);
}

int main(void) {
  append("AAAAA",5,6);
  return 0;/* Handle error */
  }
}

Compliant Solution

...

(realloc())

In this compliant solution, buf refers Correcting the above example is an exercise in documentation. Since realloc is used to resize the memory pointed to by buf, the function append has the precondition that buf must point to dynamically allocated memory.:

/* NOTE: buf must point to dynamically allocated memory */

void append(char *buf, size_t count, size_t size#include <stdlib.h>
 
enum { BUFSIZE = 256 };
 
void f(void) {
  char *linebuf = " <- THIS IS A LINE"(char *)malloc(BUFSIZE * sizeof(char));
  int line_lenchar *p = strlen(line);

  if ((count + line_len) > size) {
    buf = realloc(buf,count+line_len);char *)realloc(buf, 2 * BUFSIZE);
  if (p == NULL) {
    size/* =Handle count + line_len;error */
  }
  strncat(buf,line,line_len);
}

int main(void) {
  size_t size = 6, count = 5;
  char *str = malloc(size);
  strncpy(str,"AAAAA", size);
  append(str,size,count);
  free(str);
  return 0;
}

Compliant Code Example 2A

Alternatively, the function append could be rewritten not to use realloc() to resize buf. This solution goes beyond the scope of this document, but is nonetheless viable and, depending on the context of the program, may be preferred.

}

Note that realloc() will behave properly even if malloc() failed, because when given a null pointer, realloc() behaves like a call to malloc().

Risk Assessment

The consequences of this error depend on the implementation, but they range from nothing to arbitrary code execution if that memory is reused by malloc(). 

Automated Detection

Related Vulnerabilities

CVE-2015-0240 describes a vulnerability in which an uninitialized pointer is passed to TALLOC_FREE(), which is a Samba-specific memory deallocation macro that wraps the talloc_free() function. The implementation of  talloc_free() would access the uninitialized pointer, resulting in a remote exploit.

Search for vulnerabilities resulting from the violation of this rule on the CERT website.

Related Guidelines

Key here (explains table format and definitions)

Bibliography

...

Image Added Image Added Image Addedj1This violates recommendation 1 (sort of)