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-2024-40670HIGHIn TBD of TBD, there is a possible use after free due to a race condition. This could lead to local escalation of privilege with no additionEPSS 0.1%CVE-2025-20802MEDIUMIn geniezone, there is a possible memory corruption due to use after free. This could lead to local escalation of privilege if a malicious aEPSS 0.1%CVE-2025-20775MEDIUMIn display, there is a possible memory corruption due to use after free. This could lead to local escalation of privilege if a malicious actEPSS 0.1%CVE-2025-20805MEDIUMIn dpe, there is a possible memory corruption due to use after free. This could lead to local escalation of privilege if a malicious actor hEPSS 0.1%CVE-2025-20804MEDIUMIn dpe, there is a possible memory corruption due to use after free. This could lead to local escalation of privilege if a malicious actor hEPSS 0.1%CVE-2024-32927HIGHIn sendDeviceState_1_6 of RadioExt.cpp, there is a possible use after free due to improper locking. This could lead to local escalation of pEPSS 0.1%CVE-2025-20806MEDIUMIn dpe, there is a possible memory corruption due to use after free. This could lead to local escalation of privilege if a malicious actor hEPSS 0.1%CVE-2025-20785MEDIUMIn display, there is a possible memory corruption due to use after free. This could lead to local escalation of privilege if a malicious actEPSS 0.1%CVE-2024-40669HIGHIn TBD of TBD, there is a possible use after free due to a race condition. This could lead to local escalation of privilege with no additionEPSS 0.1%CVE-2025-20772MEDIUMIn display, there is a possible memory corruption due to use after free. This could lead to local escalation of privilege if a malicious actEPSS 0.1%CVE-2024-47017HIGHIn ufshc_scsi_cmd of ufs.c, there is a possible stack variable use after free due to a use after free. This could lead to local escalation oEPSS 0.1%CVE-2025-58311MEDIUMUAF vulnerability in the USB driver module. Impact: Successful exploitation of this vulnerability will affect availability and confidentialiEPSS 0.1%CVE-2025-47339HIGHUse After Free in HLOSEPSS 0.1%CVE-2025-58307MEDIUMUAF vulnerability in the screen recording framework module. Impact: Successful exploitation of this vulnerability may affect availability.EPSS 0.1%CVE-2026-20443MEDIUMIn display, there is a possible memory corruption due to use after free. This could lead to local escalation of privilege if a malicious actEPSS 0.1%CVE-2026-56914HIGHIn multiple locations, there is a possible use-after-free due to improper locking. This could lead to local escalation of privilege with no EPSS 0.1%CVE-2025-20799HIGHIn c2ps, there is a possible memory corruption due to use after free. This could lead to local escalation of privilege if a malicious actor EPSS 0.1%CVE-2018-9417HIGHIn f_hidg_read and hidg_disable of f_hid.c, there is a possible use-after-free due to improper locking. This could lead to local escalation EPSS 0.1%CVE-2025-20745MEDIUMIn apusys, there is a possible memory corruption due to use after free. This could lead to local escalation of privilege if a malicious actoEPSS 0.1%CVE-2025-36922MEDIUMIn bigo_map of bigo_iommu.c, there is a possible information disclosure due to a use after free. This could lead to local escalation of priEPSS 0.1%