Skip to content
OpenAdvisories

Weakness (CWE)

CWE-763: Release of Invalid Pointer or Reference

Base Incomplete

The product attempts to return a memory resource to the system, but it calls the wrong release function or calls the appropriate release function incorrectly.

How to prevent it (4 mitigations)
  1. 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().

  2. Implementation

    When programming in C++, consider using smart pointers provided by the boost library to help correctly and consistently manage memory.

  3. 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.

  4. Architecture and Design

    Use a language that provides abstractions for memory allocation and deallocation.

Source: MITRE CWE-763

1 result · Clear filters · Feed

  • Medium 4.3
    CVE-2026-15718 Public exploit

    Invalid pointer in the JavaScript: WebAssembly component

    We are aware that exploit code for this is public however we are not aware of any attacks in the wild abusing this flaw. This vulnerability was fixed in Firefox 152.0.6, Firefox ESR 140.13, and Thunderbird 140.13.