Vulnerabilidades em MediaTek, Inc.

1.103 resultados
Análise Vexday

Com 957 CVEs catalogadas, o histórico de vulnerabilidades da MediaTek, Inc. é extenso, embora a taxa de exploração ativa registrada esteja abaixo da média geral do catálogo CISA KEV — nenhuma CVE confirmada em exploração ativa no momento. O ponto de maior atenção é CVE-2024-20017, classificada como a vulnerabilidade mais perigosa no portfólio atual, com score EPSS de 0,4633, indicando probabilidade relevante de exploração em curto prazo. O tipo de falha mais recorrente é CWE-787 (escrita fora dos limites de memória), padrão que historicamente favorece execução de código arbitrário e eleva o risco de impacto crítico quando explorado. Com 30 CVEs de severidade crítica e 2 com PoC pública disponível, equipes responsáveis por dispositivos baseados em chipsets MediaTek devem priorizar a triagem dessas vulnerabilidades, especialmente as que combinam alta criticidade com código de prova de conceito acessível.

CVE-2025-20778HIGHIn display, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of privilege if a malEPSS 0.1%CVE-2025-20657MEDIUMIn vdec, there is a possible permission bypass due to improper input validation. This could lead to local escalation of privilege if a malicEPSS 0.1%CVE-2025-20749MEDIUMIn charger, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of privilege if a malEPSS 0.1%CVE-2025-20771MEDIUMIn display, there is a possible escalation of privilege due to improper input validation. This could lead to local escalation of privilege iEPSS 0.1%CVE-2022-20013—In vow driver, there is a possible memory corruption due to a race condition. This could lead to local escalation of privilege with System eEPSS 0.1%CVE-2025-20641HIGHIn DA, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of privilege, if an attackEPSS 0.1%CVE-2025-20779HIGHIn display, there is a possible use after free due to a race condition. This could lead to local escalation of privilege if a malicious actoEPSS 0.1%CVE-2024-20136MEDIUMIn da, there is a possible out of bounds read due to a missing bounds check. This could lead to local information disclosure with no additioEPSS 0.1%CVE-2022-26451—In ged, there is a possible use after free due to improper locking. This could lead to local escalation of privilege with System execution pEPSS 0.1%CVE-2024-20032MEDIUMIn aee, there is a possible permission bypass due to a missing permission check. This could lead to local escalation of privilege with SysteEPSS 0.1%CVE-2022-20082—In GPU, there is a possible use after free due to a race condition. This could lead to local escalation of privilege with no additional execEPSS 0.1%CVE-2023-32873MEDIUMIn keyInstall, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of privilege with EPSS 0.1%CVE-2023-20625MEDIUMIn adsp, there is a possible double free due to a race condition. This could lead to local escalation of privilege with System execution priEPSS 0.1%CVE-2022-20090—In aee driver, there is a possible use after free due to a race condition. This could lead to local escalation of privilege with System execEPSS 0.1%CVE-2024-20106MEDIUMIn m4u, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of privilege with System EPSS 0.1%CVE-2025-20668MEDIUMIn scp, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of privilege if a malicioEPSS 0.1%CVE-2023-20717MEDIUMIn vcu, there is a possible leak of dma buffer due to a race condition. This could lead to local information disclosure with System executioEPSS 0.1%CVE-2025-20665MEDIUMIn devinfo, there is a possible information disclosure due to a missing SELinux policy. This could lead to local information disclosure of dEPSS 0.1%CVE-2022-20091—In aee driver, there is a possible use after free due to a race condition. This could lead to local escalation of privilege with System execEPSS 0.1%CVE-2022-20110—In ion, there is a possible use after free due to a race condition. This could lead to local escalation of privilege with no additional execEPSS 0.1%