Skip to main content
GitHub

MEM31-C. Free dynamically allocated memory when no longer needed

Before the lifetime of the last pointer that stores the return value of a call to a standard memory allocation function has ended, it must be matched by a call to free() with that pointer value.

Noncompliant Code Example

In this noncompliant example, the object allocated by the call to malloc() is not freed before the end of the lifetime of the last pointer text_buffer referring to the object:

Non-compliant code
#include <stdlib.h>
 
enum { BUFFER_SIZE = 32 };

int f(void) {
  char *text_buffer = (char *)malloc(BUFFER_SIZE); 
  if (text_buffer == NULL) {
    return -1;
  }
  return 0;
}

Compliant Solution

In this compliant solution, the pointer is deallocated with a call to free() :

Compliant code
#include <stdlib.h>

enum { BUFFER_SIZE = 32 };

int f(void) {
  char *text_buffer = (char *)malloc(BUFFER_SIZE); 
  if (text_buffer == NULL) {
    return -1;
  }
 
  free(text_buffer);
  return 0;
}

Exceptions

MEM31-C-EX1 : Allocated memory does not need to be freed if it is assigned to a pointer whose lifetime includes program termination. The following code example illustrates a pointer that stores the return value from malloc() in a static variable:

Compliant code
#include <stdlib.h>
 
enum { BUFFER_SIZE = 32 };

int f(void) {
  static char *text_buffer = NULL;
  if (text_buffer == NULL) {
    text_buffer = (char *)malloc(BUFFER_SIZE); 
    if (text_buffer == NULL) {
      return -1;
    }
  }
  return 0;
}

Risk Assessment

Failing to free memory can result in the exhaustion of system memory resources, which can lead to a denial-of-service attack .

Rule Severity Likelihood Detectable Repairable Priority Level
MEM31-C Medium Probable No No P4 L3

Automated Detection

ToolVersionCheckerDescription
Astrée
25.10
csa-memory-leak (C++)Supported, but no explicit checker
Partially checked (C++)
Axivion Suite
7.12.0
CertC-MEM31Can detect dynamically allocated resources that are not freed
CodeSonar
9.2p0
ALLOC.LEAKLeak
Compass/ROSE
Coverity
2017.07
RESOURCE_LEAK
ALLOC_FREE_MISMATCH
Finds resource leaks from variables that go out of scope while owning a resource
Cppcheck
2.15
memleak
leakReturnValNotUsed
leakUnsafeArgAlloc
memleakOnRealloc
Cppcheck Premium
24.11.0
memleak
leakReturnValNotUsed
leakUnsafeArgAlloc
memleakOnRealloc
Helix QAC
2025.2
DF2706, DF2707, DF2708
C++3337, C++3338
Klocwork
2025.2
CL.FFM.ASSIGN
CL.FFM.COPY
CL.SHALLOW.ASSIGN
CL.SHALLOW.COPY
FMM.MIGHT
FMM.MUST
LDRA tool suite
9.7.1
50 DPartially implemented
Parasoft C/C++test
2026.1
CERT_C-MEM31-aEnsure resources are freed
Parasoft Insure++Runtime analysis
PC-lint Plus
1.4
429Fully supported
Polyspace Bug Finder
R2025b
CERT C: Rule MEM31-CChecks for memory leak (rule fully covered)
PVS-Studio
7.43
V773
RuleChecker
25.10
csa-memory-leak (C++)Partially checked
Security Reviewer - Static Reviewer
6.02
CPP_17
CPP_18
CPP_22
CPP_23
CPP_24
CPP_25
CPP_26
CPP_27
Fully implemented
SonarQube C/C++ Plugin
3.11
S3584
Splint
3.1.1
TrustInSoft Analyzer
1.38
mallocExhaustively verified.

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

Key here (explains table format and definitions)

TaxonomyTaxonomy itemRelationship
ISO/IEC TR 24772:2013Memory Leak [XYL]Prior to 2018-01-12: CERT: Unspecified Relationship
ISO/IEC TS 17961Failing to close files or free dynamic memory when they are no longer needed [fileclose]Prior to 2018-01-12: CERT: Unspecified Relationship
CWE 2.11CWE-401 , Improper Release of Memory Before Removing Last Reference ("Memory Leak")2017-07-05: CERT: Exact
CWE 2.11CWE-4042017-07-06: CERT: Rule subset of CWE
CWE 2.11CWE-4592017-07-06: CERT: Rule subset of CWE
CWE 2.11CWE-7712017-07-06: CERT: Rule subset of CWE
CWE 2.11CWE-7722017-07-06: CERT: Rule subset of CWE

CERT-CWE Mapping Notes

Key here for mapping notes

CWE-404/CWE-459/CWE-771/CWE-772 and FIO42-C/MEM31-C

Intersection( FIO42-C, MEM31-C) = Ø

CWE-404 = CWE-459 = CWE-771 = CWE-772

CWE-404 = Union( FIO42-C, MEM31-C list) where list =

  • Failure to free resources besides files or memory chunks, such as mutexes)

Bibliography

[ ISO/IEC 9899:2024 ]Subclause 7.24.3, "Memory Management Functions"