Falhas do tipo CWE-416

5.043 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-2022-37359HIGHThis vulnerability allows remote attackers to execute arbitrary code on affected installations of PDF-XChange Editor. User interaction is reEPSS 0.8%CVE-2022-37374HIGHThis vulnerability allows remote attackers to execute arbitrary code on affected installations of PDF-XChange Editor. User interaction is reEPSS 0.8%CVE-2018-10876MEDIUMA flaw was found in Linux kernel in the ext4 filesystem code. A use-after-free is possible in ext4_ext_remove_space() function when mountingEPSS 0.8%CVE-2025-43222CRITICALA use-after-free issue was addressed by removing the vulnerable code. This issue is fixed in iPadOS 17.7.9, macOS Sequoia 15.6, macOS SonomaEPSS 0.8%CVE-2023-0699HIGHUse after free in GPU in Google Chrome prior to 110.0.5481.77 allowed a remote attacker to potentially exploit heap corruption via a craftedEPSS 0.8%CVE-2024-5494HIGHUse after free in Dawn in Google Chrome prior to 125.0.6422.141 allowed a remote attacker to potentially exploit heap corruption via a craftEPSS 0.8%CVE-2022-3198HIGHUse after free in PDF in Google Chrome prior to 105.0.5195.125 allowed a remote attacker to potentially exploit heap corruption via a crafteEPSS 0.8%CVE-2022-48666CRITICALscsi: core: Fix a use-after-freeEPSS 0.8%CVE-2023-38669HIGHUse after free in paddle.diagonal in PaddlePaddle before 2.5.0. This resulted in a potentially exploitable condition. EPSS 0.8%CVE-2024-49021HIGHMicrosoft SQL Server Remote Code Execution VulnerabilityEPSS 0.8%CVE-2023-1528HIGHUse after free in Passwords in Google Chrome prior to 111.0.5563.110 allowed a remote attacker who had compromised the renderer process to pEPSS 0.8%CVE-2022-3886HIGHUse after free in Speech Recognition in Google Chrome prior to 107.0.5304.106 allowed a remote attacker to potentially exploit heap corruptiEPSS 0.8%CVE-2024-49027HIGHMicrosoft Excel Remote Code Execution VulnerabilityEPSS 0.8%CVE-2021-32495CRITICALRadare2 has a use-after-free vulnerability in pyc parser's get_none_object function. Attacker can read freed memory afterwards. This will alEPSS 0.8%CVE-2026-34332HIGHWindows Kernel-Mode Driver Remote Code Execution VulnerabilityEPSS 0.8%CVE-2025-43368MEDIUMA use-after-free issue was addressed with improved memory management. This issue is fixed in Safari 26, iOS 26 and iPadOS 26, macOS Tahoe 26EPSS 0.8%CVE-2025-29820HIGHMicrosoft Word Remote Code Execution VulnerabilityEPSS 0.8%CVE-2026-27950MEDIUMFreeRDP heap-use-after-free in update_pointer_new(SDL): Fix Applied in the Wrong FileEPSS 0.8%CVE-2023-21822HIGHWindows Graphics Component Elevation of Privilege VulnerabilityEPSS 0.8%CVE-2023-2461HIGHUse after free in OS Inputs in Google Chrome on ChromeOS prior to 113.0.5672.63 allowed a remote attacker who convinced a user to enage in sEPSS 0.8%