Falhas do tipo CWE-416

5.142 resultados

Uso após liberação de memória

Ocorre quando o código tenta acessar (ler ou escrever) um bloco de memória que já foi liberado (free, delete). O programa mantém um ponteiro para a memória, mas o sistema operacional pode reatribuir essa região para outro uso, causando corrupção de dados, travamento ou execução de código arbitrário.

Exemplo

Um servidor web aloca memória para armazenar dados de sessão do usuário, depois libera essa memória quando a sessão encerra. Se uma thread continuar tentando acessar essa sessão após a liberação, pode ler dados de outra sessão ou sobrescrever dados críticos de outro processo.

Como mitigar

Sempre anule ponteiros após liberar memória (ptr = NULL), use variáveis de controle para rastrear estado de alocação, implemente gerenciamento automático de memória quando possível (smart pointers em C++), e execute testes com sanitizers (AddressSanitizer, Valgrind) durante desenvolvimento e CI/CD.

CVE-2025-6349MEDIUMMali GPU Kernel Driver allows improper GPU memory processing operationsEPSS 0.2%CVE-2025-0015HIGHMali GPU Kernel Driver allows improper GPU processing operationsEPSS 0.2%CVE-2026-95298HIGHUse after free in Browser in Google Chrome prior to 154.0.8037.57 allowed a local attacker to potentially execute arbitrary code outside theEPSS 0.2%CVE-2024-3655HIGHMali GPU Kernel Driver allows improper GPU memory processing operationsEPSS 0.2%CVE-2024-33060HIGHUse After Free in DSP ServiceEPSS 0.2%CVE-2025-23402HIGHA vulnerability has been identified in Teamcenter Visualization V14.3 (All versions < V14.3.0.13), Teamcenter Visualization V2312 (All versiEPSS 0.2%CVE-2026-12366HIGHUse-after-free freeing an armed dynamically-allocated k_timer in Zephyr userspace object disposalEPSS 0.2%CVE-2026-7338HIGHUse after free in Cast in Google Chrome prior to 147.0.7727.138 allowed an attacker on the local network segment to potentially exploit heapEPSS 0.2%CVE-2025-47342HIGHUse After Free in BT ControllerEPSS 0.2%CVE-2022-20502MEDIUMIn GetResolvedMethod of entrypoint_utils-inl.h, there is a possible use after free due to a stale cache. This could lead to local informatioEPSS 0.2%CVE-2026-10635MEDIUMDangling memory-domain pointer (use-after-free) in Xtensa MMU page-table code on memory-domain de-initEPSS 0.2%CVE-2025-0835HIGHGPU DDK - _WrapExtMemReleasePages called twice if _FlushUMVirtualRange failsEPSS 0.2%CVE-2022-22058HIGHMemory corruption due to use after free issue in kernel while processing ION handles in Snapdragon Auto, Snapdragon Compute, Snapdragon ConnEPSS 0.2%CVE-2023-53235HIGHdrm/tests: helpers: Avoid a driver uafEPSS 0.2%CVE-2024-23380HIGHUse After Free in GraphicsEPSS 0.2%CVE-2026-34757MEDIUMLIBPNG has a yse-after-free in png_set_PLTE, png_set_tRNS and png_set_hIST leading to corrupted chunk data and potential heap information disclosureEPSS 0.2%CVE-2026-73282MEDIUMIn ssh in OpenSSH before 10.5, a use-after-free for realloc data can occur if a certain pair of remote-forwarding operations are concurrent.EPSS 0.2%CVE-2021-37690MEDIUMUse after free and segfault in shape inference functions in TensorFlowEPSS 0.2%CVE-2022-50423HIGHACPICA: Fix use-after-free in acpi_ut_copy_ipackage_to_ipackage()EPSS 0.2%CVE-2022-50411HIGHACPICA: Fix error code path in acpi_ds_call_control_method()EPSS 0.2%