이름: Mismatched Memory Management Routines

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.

일반 정보

취약점 도입 방식

Implementation

적용 가능한 플랫폼

언어

클래스: Memory-Unsafe (Often)
이름: C (Undetermined)
이름: C++ (Undetermined)

일반적인 결과

범위	영향	가능성
Integrity Availability Confidentiality	Modify Memory, DoS: Crash, Exit, or Restart, Execute Unauthorized Code or Commands 참고: 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.

관찰된 예시

참고 자료	설명
CVE-2025-11015	3D engine rendering backend performs a delete[] on a buffer that was allocated using malloc()

잠재적 완화 방법

Phases : 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().
Phases : Implementation
Phases : Architecture and Design
Phases : Architecture and Design
Use a language that provides abstractions for memory allocation and deallocation.

탐지 방법

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 valgrind [REF-480].
효과성 : Moderate

취약점 매핑 메모

근거 : This CWE entry is at the Variant level of abstraction, which is a preferred level of abstraction for mapping to the root causes of vulnerabilities.
댓글 : Carefully read both the name and description to ensure that this mapping is an appropriate fit. Do not try to 'force' a mapping to a lower-level Base/Variant simply to comply with this preferred level of abstraction.

메모

참고 자료

제출

이름	조직	날짜	출시일	Version
CWE Content Team	MITRE	2009-05-08 +00:00	2009-05-27 +00:00	1.4

수정 사항

이름	조직	날짜	댓글
CWE Content Team	MITRE	2009-12-28 +00:00	updated Applicable_Platforms, Likelihood_of_Exploit
CWE Content Team	MITRE	2010-06-21 +00:00	updated Description, Potential_Mitigations
CWE Content Team	MITRE	2011-06-01 +00:00	updated Common_Consequences
CWE Content Team	MITRE	2011-09-13 +00:00	updated Relationships, Taxonomy_Mappings
CWE Content Team	MITRE	2012-05-11 +00:00	updated Demonstrative_Examples, Relationships
CWE Content Team	MITRE	2012-10-30 +00:00	updated Potential_Mitigations
CWE Content Team	MITRE	2014-02-18 +00:00	updated Demonstrative_Examples, Potential_Mitigations, References
CWE Content Team	MITRE	2014-07-30 +00:00	updated Relationships, Taxonomy_Mappings
CWE Content Team	MITRE	2017-11-08 +00:00	updated Applicable_Platforms, References, Taxonomy_Mappings
CWE Content Team	MITRE	2019-01-03 +00:00	updated Relationships
CWE Content Team	MITRE	2020-02-24 +00:00	updated Relationships
CWE Content Team	MITRE	2020-12-10 +00:00	updated Relationships
CWE Content Team	MITRE	2021-03-15 +00:00	updated Relationships
CWE Content Team	MITRE	2023-01-31 +00:00	updated Description
CWE Content Team	MITRE	2023-04-27 +00:00	updated References, Relationships
CWE Content Team	MITRE	2023-06-29 +00:00	updated Mapping_Notes
CWE Content Team	MITRE	2025-09-09 +00:00	updated Functional_Areas, References
CWE Content Team	MITRE	2025-12-11 +00:00	updated Applicable_Platforms, Detection_Factors, Potential_Mitigations, References, Weakness_Ordinalities
CWE Content Team	MITRE	2026-04-30 +00:00	updated Detection_Factors
CWE Content Team	MITRE	2026-10-28 +00:00	updated Common_Consequences, Description, Observed_Examples, Technical_Nuance

CWE-762 상세 정보

CWE-762