Weaknesses of type CWE-416

5,184 results

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

Ocorre quando o código tenta acessar um bloco de memória que já foi desalocado (free/delete). O ponteiro continua apontando para aquele endereço, mas o dado ali pode ter sido sobrescrito por outra operação, causando comportamento impredizível, corrupção de dados ou execução de código arbitrário.

Example

Um buffer é alocado, depois liberado com free(). Mais adiante, o código ainda tenta ler ou escrever naquele mesmo ponteiro sem verificar. Se um atacante controlar a alocação subsequente daquele endereço, consegue manipular o conteúdo que será lido.

How to mitigate

Anule o ponteiro imediatamente após liberar (ptr = NULL), implemente análise estática para detectar acessos pós-liberação, use ferramentas como valgrind ou AddressSanitizer nos testes, e considere linguagens com gerenciamento automático de memória para código sensível.

CVE-2026-56988MEDIUMIn multiple functions of bluetooth_cco.cc, there is a possible use-after-free due to a race condition. This could lead to local escalation oEPSS 0.1%CVE-2025-66326MEDIUMRace condition vulnerability in the audio module. Impact: Successful exploitation of this vulnerability may affect availability.EPSS 0.1%CVE-2026-58724HIGHIn multiple locations, there is a possible use-after-free due to a race condition. This could lead to local escalation of privilege with SysEPSS 0.1%CVE-2023-20835MEDIUMIn camsys, there is a possible use after free due to a race condition. This could lead to local escalation of privilege with System executioEPSS 0.1%CVE-2023-20834MEDIUMIn pda, there is a possible use after free due to a race condition. This could lead to local escalation of privilege with System execution pEPSS 0.1%CVE-2026-0125HIGHIn multiple functions of vpu_ioctl.c, there is a possible use after free due to a race condition. This could lead to local escalation of priEPSS 0.1%CVE-2025-47374MEDIUMUse After Free in Camera DriverEPSS 0.1%CVE-2026-0112HIGHIn vpu_open_inst of vpu_ioctl.c, there is a possible use after free due to a race condition. This could lead to local escalation of privilegEPSS 0.1%CVE-2026-0121LOWIn VPU, there is a possible use-after-free read due to a race condition. This could lead to local information disclosure with no additional EPSS 0.1%CVE-2026-106281CRITICALUse after free in Tint in Google Chrome prior to 155.0.8059.39 allowed a remote attacker to potentially execute arbitrary code outside the sEPSS —CVE-2026-106190HIGHUse after free in Media in Google Chrome prior to 155.0.8059.39 allowed a remote attacker to execute arbitrary code inside the sandbox via aEPSS —CVE-2026-106358CRITICALUse after free in Navigation in Google Chrome prior to 155.0.8059.39 allowed a remote attacker to execute arbitrary code outside the sandboxEPSS —CVE-2026-106278HIGHUse after free in Select in Google Chrome prior to 155.0.8059.39 allowed a remote attacker leveraging social engineering to execute arbitrarEPSS —CVE-2026-106335HIGHUse after free in Media in Google Chrome prior to 155.0.8059.39 allowed a remote attacker to execute arbitrary code inside the sandbox via aEPSS —CVE-2026-106248HIGHUse after free in Bindings in Google Chrome prior to 155.0.8059.39 allowed a remote attacker to execute arbitrary code inside the sandbox viEPSS —CVE-2026-106257HIGHUse after free in HTML in Google Chrome prior to 155.0.8059.39 allowed a remote attacker to execute arbitrary code inside the sandbox via a EPSS —CVE-2026-106269HIGHUse after free in CSS in Google Chrome prior to 155.0.8059.39 allowed a remote attacker to execute arbitrary code inside the sandbox via a cEPSS —CVE-2026-106204HIGHUse after free in PDF in Google Chrome prior to 155.0.8059.39 allowed a remote attacker to execute arbitrary code inside the sandbox via a cEPSS —CVE-2026-106423HIGHUse after free in Media in Google Chrome prior to 155.0.8059.39 allowed a remote attacker to execute arbitrary code inside the sandbox via aEPSS —CVE-2026-106411HIGHUse after free in Parser in Google Chrome prior to 155.0.8059.39 allowed a remote attacker to execute arbitrary code inside the sandbox via EPSS —