CyberSecBulletin

Mismatched Memory Management Routines

CWE-762

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.

We track 7 vulnerabilities of this type. 100% are rated high or critical, and the average CVSS score is 7.7.

How this weakness is prevented

  • 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().
  • Implementation: Choose a language or tool that provides automatic memory management, or makes manual memory management less error-prone. For example, glibc in Linux provides protection against free of invalid pointers. When using Xcode to target OS X or iOS, enable automatic reference counting (ARC). To help correctly and consistently manage memory when programming in C++, consider using a smart pointer class such as std
  • 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.
  • Architecture and Design: Use a language that provides abstractions for memory allocation and deallocation.

Latest Mismatched Memory Management Routines vulnerabilities

  • 7.5 High severity

    Junos OS: Mismatched Memory Management Routines

    CVE-2026-102025Juniper Networks

    A Mismatched Memory Management Routines vulnerability in the routing protocol daemon (rpd) process of Juniper Networks Junos OS and Junos OS Evolved allows an authenticated network-based attacker to cause a denial of service via a BGP route update when extende

  • 7.8 High severity

    llama.cpp: Double Free

    CVE-2026-43622Ggml-org

    llama.cpp builds b1886 through b7445 contain a double free vulnerability in the LLaMA-Android JNI wrapper where new_1batch() allocates memory using malloc() while free_1batch() deallocates it using the C++ delete operator, causing heap metadata corruption. Att

  • 7.5 High severity

    Apache Thrift: Mismatched Memory Management Routines

    CVE-2025-48431ApacheEPSS 1.04%

    Mismatched Memory Management Routines vulnerability in Apache Thrift c_glib language bindings. This issue affects Apache Thrift: before 0.23.0. Users are recommended to upgrade to version 0.23.0, which fixes the issue. Description: Specially crafted requests c

  • 7.5 High severity

    Secure Access: Mismatched Memory Management Routines

    CVE-2025-49080Absolute Security

    There is a memory management vulnerability in Absolute Secure Access server versions 9.0 to 13.54. Attackers with network access to the server can cause a Denial of Service by sending a specially crafted sequence of packets to the server. The attack complexity

  • 7.4 High severity

    Cisco IOS XE Software: Mismatched Memory Management Routines

    CVE-2025-20189Cisco

    A vulnerability in the Cisco Express Forwarding functionality of Cisco IOS XE Software for Cisco ASR 903 Aggregation Services Routers with Route Switch Processor 3 (RSP3C) could allow an unauthenticated, adjacent attacker to trigger a denial of service (DoS) c

  • 7.8 High severity

    exynos_850: Use After Free

    CVE-2024-32503Samsung

    An issue was discovered in Samsung Mobile Processor and Wearable Processor Exynos 850, Exynos 1080, Exynos 2100, Exynos 1280, Exynos 1380, Exynos 1330, Exynos W920, Exynos W930. The mobile processor lacks proper memory deallocation checking, which can result i

  • 8.1 High severity

    redis: Integer Overflow or Wraparound

    CVE-2023-41056RedisEPSS 2.56%

    Redis is an in-memory database that persists on disk. Redis incorrectly handles resizing of memory buffers which can result in integer overflow that leads to heap overflow and potential remote code execution. This issue has been patched in version 7.0.15 and 7