Vulnerabilidades en MediaTek, Inc.

1016 resultados
Análisis 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-20695MEDIUMIn Bluetooth FW, there is a possible system crash due to an uncaught exception. This could lead to remote denial of service with no additionEPSS 0.2%CVE-2022-21789—In audio ipi, there is a possible memory corruption due to a race condition. This could lead to local escalation of privilege with System exEPSS 0.2%CVE-2026-20462MEDIUMIn Telephony, there is a possible memory corruption due to a heap buffer overflow. This could lead to local escalation of privilege if a malEPSS 0.2%CVE-2026-20469MEDIUMIn trusted_mem, there is a possible escalation of privilege due to improper input validation. This could lead to local escalation of privileEPSS 0.2%CVE-2026-20468MEDIUMIn apusys, there is a possible escalation of privilege due to a confused deputy. This could lead to local escalation of privilege if a malicEPSS 0.2%CVE-2026-20485MEDIUMIn HFRP, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of privilege if a maliciEPSS 0.2%CVE-2022-26468—In preloader (usb), there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of privilege,EPSS 0.2%CVE-2022-32643MEDIUMIn ccd, 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.2%CVE-2026-20484MEDIUMIn TFA, there is a possible information disclosure due to a missing permission check. This could lead to local information disclosure if a mEPSS 0.2%CVE-2026-20451MEDIUMIn slbc, there is a possible out of bounds write due to type confusion. This could lead to local escalation of privilege if a malicious actoEPSS 0.2%CVE-2025-20687MEDIUMIn Bluetooth driver, there is a possible out of bounds read due to an incorrect bounds check. This could lead to local denial of service witEPSS 0.2%CVE-2026-20496MEDIUMIn geniezone, there is a possible out of bounds read due to a missing bounds check. This could lead to local information disclosure if a malEPSS 0.1%CVE-2026-20495HIGHIn Bluetooth driver, there is a possible permission bypass due to a missing permission check. This could lead to local escalation of privileEPSS 0.1%CVE-2025-20676MEDIUMIn wlan STA driver, there is a possible system crash due to an uncaught exception. This could lead to local denial of service with User execEPSS 0.1%CVE-2025-20675MEDIUMIn wlan STA driver, there is a possible system crash due to an uncaught exception. This could lead to local denial of service with User execEPSS 0.1%CVE-2025-20739MEDIUMIn wlan AP driver, there is a possible out of bounds write due to an incorrect bounds check. This could lead to local escalation of privilegEPSS 0.1%CVE-2025-20741MEDIUMIn wlan AP driver, there is a possible out of bounds write due to an incorrect bounds check. This could lead to local escalation of privilegEPSS 0.1%CVE-2025-20738MEDIUMIn wlan AP driver, there is a possible out of bounds write due to an incorrect bounds check. This could lead to local escalation of privilegEPSS 0.1%CVE-2022-20025—In Bluetooth, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of privilege with nEPSS 0.1%CVE-2026-20491MEDIUMIn med, there is a possible out of bounds write due to an incorrect bounds check. This could lead to local denial of service with User execuEPSS 0.1%