Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Memory is a limited resource and can be exhausted. Available memory is typically bounded by the sum of the amount of physical memory and the swap space allocated to the operating system by the administrator. For example, a system with 1GB of physical memory configured with 2GB of swap space may be able to allocate, at most, 3GB of heap space total to all running processes (minus the size of the operating system itself and the text and data segments of all running processes). Once all virtual memory has been allocated, requests for more memory will fail. As discussed in void MEM32ERR33-C. Detect and handle memory allocation standard library errors, programs that fail to check for and properly handle memory allocation failures will have undefined behavior and are likely to crash when heap space is exhausted. Heap exhaustion can result from

...

Tool

Version

Checker

Description

CodeSonar
Include Page
CodeSonar_V
CodeSonar_V

ALLOC.LEAK
ALLOC.SIZE.SUBUFLOW
IO.TAINT.SIZE
MISC.MEM.SIZE.BAD
(general)

Leak
Subtraction Underflow underflow of Allocation Sizeallocation size
Tainted Allocation Sizeallocation size
Unreasonable Size Argumentsize argument
Library models account for allocator failure cases.

LDRA tool suite
Include Page
LDRA_V
LDRA_V

26 S, 140 S, 6 D, 28 D, 5 C, 1 U

Partially Implementedimplemented

Related Vulnerabilities

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

...