CyberSecBulletin

Use After Free

CWE-416

The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory belongs to the code that operates on the new pointer.

We track 4,465 vulnerabilities of this type. 100% are rated high or critical, and the average CVSS score is 8.3. 109 have been exploited in real attacks.

How this weakness is prevented

  • Architecture and Design: Choose a language that provides automatic memory management.
  • Implementation: When freeing pointers, be sure to set them to NULL once they are freed. However, the utilization of multiple or complex data structures may lower the usefulness of this strategy.

Latest Use After Free vulnerabilities

  • 8.4 High severity

    Android: Use After Free

    CVE-2026-58942Google

    In do_fault_around of memory.c, there is a possible use after free due to a logic error in the code. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

  • 9.8 Critical severity

    Android: Use After Free

    CVE-2026-58936Google

    In png_set_tRNS of pngset.c, there is a possible memory corruption due to a use-after-free. This could lead to remote code execution with no additional execution privileges needed. User interaction is not needed for exploitation.

  • 9.8 Critical severity

    Android: Use After Free

    CVE-2026-58876Google

    In multiple locations, there is a possible memory safety issue due to a use-after-free. This could lead to remote code execution with no additional execution privileges needed. User interaction is not needed for exploitation.

  • 8.1 High severity

    Android: Concurrent Execution using Shared Resource with Improper Synchronization

    CVE-2026-58857Google

    In decrypt of CryptoHalHidl.cpp, there is a possible use-after-free due to a race condition. This could lead to remote code execution with no additional execution privileges needed. User interaction is not needed for exploitation.

  • 8.4 High severity

    Android: Use After Free

    CVE-2026-58829Google

    In fuse_backing_mmap of backing.c, there is a possible memory corruption due to a use after free. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

  • 8.4 High severity

    Android: Use After Free

    CVE-2026-58828Google

    In multiple functions of base.c, there is a possible use-after-free due to a race condition. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

  • 8.4 High severity

    Android: Use After Free

    CVE-2026-58827Google

    In multiple functions of dma-buf.c, there is a possible use after free due to a race condition. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

  • 8.4 High severity

    Android: Use After Free

    CVE-2026-58826Google

    In ksys_unshare of fork.c, there is a possible memory corruption due to a use after free. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

  • 8.4 High severity

    Android: Use After Free

    CVE-2026-58825Google

    In multiple functions of fork.c, there is a possible use after free due to a logic error in the code. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

  • 8.4 High severity

    Android: Use After Free

    CVE-2026-55283Google

    In multiple locations, there is a possible memory safety issue due to a use-after-free. This could lead to remote escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

  • 8.4 High severity

    Android: Use After Free

    CVE-2026-55275Google

    In multiple locations, there is a possible use-after-free due to a race condition. This could lead to remote escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

  • 7.3 High severity

    O-KAM SuperIPCam: Improper Restriction of Operations within the Bounds of a Memory Buffer

    CVE-2026-120337VStarcam

    A vulnerability was determined in VStarcam O-KAM SuperIPCam 1.3.3.32. Affected by this issue is the function FUN_005a2d44 of the file SuperIPCam.exe of the component P2P Session Teardown. This manipulation causes use after free. The attack can be initiated rem

  • 8.4 High severity

    MediaTek chipset: Use After Free

    CVE-2026-20591MediaTek

    In GPU pdma, there is a possible escalation of privilege due to a missing permission check. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation. Patch ID: ALPS11365075

  • 7.8 High severity

    MediaTek chipset: Use After Free

    CVE-2026-20559MediaTek

    In GPU pdma, there is a possible memory corruption due to use after free. This could lead to local escalation of privilege with User execution privileges needed. User interaction is not needed for exploitation. Patch ID: ALPS11365081; Issue ID: MSV-9545.

  • 8.4 High severity

    MediaTek chipset: Use After Free

    CVE-2026-20558MediaTek

    In GPU pdma, there is a possible escalation of privilege due to use after free. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation. Patch ID: ALPS11365070; Issue ID:

  • 8.8 High severity

    ladybird: Use After Free

    CVE-2026-119332LadybirdBrowser

    Ladybird is a truly independent web browser. Prior to 209579c96473c75bd5eba9701fcadb841a045964, FinalizationRegistry::cleanup() in Libraries/LibJS/Runtime/FinalizationRegistry.cpp removed a dead record from m_records, retained an iterator to the next Finalizat

  • 7.8 High severity

    kmstool-enclave: Double Free

    CVE-2026-119116AWS

    A use-after-free and double-free issue in the SetClient command handler of the kmstool-enclave sample application of AWS aws-nitro-enclaves-sdk-c before 0.4.6 may allow an application that runs on the parent EC2 instance to corrupt heap memory inside a Nitro E

  • 7.1 High severity

    Graphics DDK: Use After Free

    CVE-2026-65586Imagination Technologies

    Software installed and run as a non-privileged user may conduct improper GPU system calls to free memory in still in use, replace with another allocation and cause arbitrary memory reads or writes to physical memory pages. A memory buffer managed by a CPU thre

  • 7.0 High severity

    Graphics DDK: Use After Free

    CVE-2026-15466Imagination Technologies

    Software installed and run as a non-privileged user may conduct improper GPU system calls to cause race condition in hardware performance counters buffer’s destruction path leading to read and/or write UAF. The race condition in the destruction path could lead

  • 8.8 High severity

    Chrome: Use After Free

    CVE-2026-119268Google

    Use after free in Editing in Google Chrome prior to 156.0.8078.79 allowed a remote attacker to execute arbitrary code inside the sandbox via a crafted HTML page. (Chromium security severity: High)

  • 8.8 High severity

    Chrome: Use After Free

    CVE-2026-119267Google

    Use after free in DOM in Google Chrome prior to 156.0.8078.79 allowed a remote attacker to execute arbitrary code inside the sandbox via a crafted HTML page. (Chromium security severity: High)

  • 8.8 High severity

    Chrome: Use After Free

    CVE-2026-119264Google

    Use after free in Dawn in Google Chrome prior to 156.0.8078.79 allowed a remote attacker to potentially execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: High)

  • 9.6 Critical severity

    Chrome: Use After Free

    CVE-2026-119263Google

    Use after free in GarbageCollection in Google Chrome prior to 156.0.8078.79 allowed a remote attacker to execute arbitrary code inside the sandbox via a crafted HTML page. (Chromium security severity: High)

  • 8.8 High severity

    Chrome: Use After Free

    CVE-2026-119260Google

    Use after free in Frames in Google Chrome prior to 156.0.8078.79 allowed a remote attacker to execute arbitrary code inside the sandbox via a crafted HTML page. (Chromium security severity: High)

  • 8.8 High severity

    Chrome: Use After Free

    CVE-2026-118359Google

    Use after free in V8 in Google Chrome prior to 156.0.8078.73 allowed a remote attacker to execute arbitrary code inside the sandbox via a crafted HTML page. (Chromium security severity: High)

  • 8.8 High severity

    Chrome: Use After Free

    CVE-2026-118358Google

    Use after free in WebAudio in Google Chrome prior to 156.0.8078.73 allowed a remote attacker to execute arbitrary code inside the sandbox via a crafted HTML page. (Chromium security severity: High)

  • 8.8 High severity

    Chrome: Use After Free

    CVE-2026-118357Google

    Use after free in FileSystem in Google Chrome prior to 156.0.8078.73 allowed a remote attacker to execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: High)

  • 8.8 High severity

    Chrome: Use After Free

    CVE-2026-118356Google

    Use after free in WTF in Google Chrome prior to 156.0.8078.73 allowed a remote attacker to potentially execute arbitrary code inside the sandbox via a crafted HTML page. (Chromium security severity: High)

  • 9.6 Critical severity

    Chrome: Use After Free

    CVE-2026-118355Google

    Use after free in Command in Google Chrome prior to 156.0.8078.73 allowed a remote attacker to execute arbitrary code inside the sandbox via a crafted HTML page. (Chromium security severity: High)

  • 8.8 High severity

    Chrome: Use After Free

    CVE-2026-118352Google

    Use after free in Cache in Google Chrome prior to 156.0.8078.73 allowed a remote attacker to execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: High)

  • 8.8 High severity

    Chrome: Use After Free

    CVE-2026-118351Google

    Use after free in Skia in Google Chrome prior to 156.0.8078.73 allowed a remote attacker to execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: High)

  • 8.8 High severity

    Chrome: Use After Free

    CVE-2026-118349Google

    Use after free in Payments in Google Chrome prior to 156.0.8078.73 allowed a remote attacker leveraging social engineering to potentially execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: High)

  • 8.8 High severity

    Chrome: Use After Free

    CVE-2026-118347Google

    Use after free in FileSystem in Google Chrome prior to 156.0.8078.73 allowed a remote attacker to potentially execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: High)

  • 8.8 High severity

    Chrome: Use After Free

    CVE-2026-118344Google

    Use after free in Layout in Google Chrome prior to 156.0.8078.73 allowed a remote attacker to execute arbitrary code inside the sandbox via a crafted HTML page. (Chromium security severity: Critical)

  • 8.8 High severity

    Chrome: Use After Free

    CVE-2026-118343Google

    Use after free in ReadingList in Google Chrome prior to 156.0.8078.73 allowed a remote attacker leveraging social engineering to execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: High)

  • 9.6 Critical severity

    Chrome: Use After Free

    CVE-2026-118342Google

    Use after free in Editing in Google Chrome prior to 156.0.8078.73 allowed a remote attacker to execute arbitrary code inside the sandbox via a crafted HTML page. (Chromium security severity: High)

  • 8.8 High severity

    Chrome: Use After Free

    CVE-2026-118341Google

    Use after free in Modularization in Google Chrome prior to 156.0.8078.73 allowed a remote attacker to execute arbitrary code inside the sandbox via a crafted HTML page. (Chromium security severity: High)

  • 8.8 High severity

    Chrome: Use After Free

    CVE-2026-118339Google

    Use after free in Animation in Google Chrome prior to 156.0.8078.73 allowed a remote attacker to execute arbitrary code inside the sandbox via a crafted HTML page. (Chromium security severity: High)

  • 9.3 Critical severity

    Chrome: Use After Free

    CVE-2026-118337Google

    Use after free in Forms in Google Chrome prior to 156.0.8078.73 allowed a remote attacker to execute arbitrary code inside the sandbox via a crafted HTML page. (Chromium security severity: High)

  • 8.8 High severity

    Chrome: Use After Free

    CVE-2026-118334Google

    Use after free in ImageCapture in Google Chrome prior to 156.0.8078.73 allowed a remote attacker to execute arbitrary code inside the sandbox via a crafted HTML page. (Chromium security severity: High)