Vulnerabilidades em MediaTek, Inc.

957 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-2023-20851—In stc, there is a possible out of bounds read due to a race condition. This could lead to local escalation of privilege with System executiEPSS 0.1%CVE-2024-20108MEDIUMIn atci, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of privilege with SystemEPSS 0.1%CVE-2024-20086HIGHIn vdec, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of privilege with SystemEPSS 0.1%CVE-2024-20115MEDIUMIn ccu, 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-2024-20099MEDIUMIn power, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of privilege with SysteEPSS 0.1%CVE-2023-20726LOWIn mnld, there is a possible leak of GPS location due to a missing permission check. This could lead to local information disclosure with noEPSS 0.1%CVE-2023-20619MEDIUMIn vcu, there is a possible memory corruption due to improper locking. This could lead to local escalation of privilege with System executioEPSS 0.1%CVE-2023-20618MEDIUMIn vcu, there is a possible memory corruption due to improper locking. This could lead to local escalation of privilege with System executioEPSS 0.1%CVE-2024-20140MEDIUMIn power, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of privilege if a malicEPSS 0.1%CVE-2025-20782MEDIUMIn 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-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-20130MEDIUMIn power, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of privilege with SysteEPSS 0.1%CVE-2024-20114MEDIUMIn ccu, 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-20803MEDIUMIn dpe, there is a possible memory corruption due to an integer overflow. This could lead to local escalation of privilege if a malicious acEPSS 0.1%CVE-2024-20109MEDIUMIn ccu, 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-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-2025-20798HIGHIn battery, 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-20807MEDIUMIn dpe, there is a possible out of bounds write due to an integer overflow. This could lead to local escalation of privilege if a malicious EPSS 0.1%CVE-2024-20118MEDIUMIn mms, there is a possible out of bounds write due to an incorrect bounds check. This could lead to local escalation of privilege with SystEPSS 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%