Vulnerabilidades em Qualcomm, Inc.

2.976 resultados
Análise Vexday

Com 2.934 CVEs catalogadas, a Qualcomm apresenta um volume expressivo de vulnerabilidades, reflexo da amplitude de seu portfólio de chipsets e firmware embarcado. A taxa de exploração ativa — 12 entradas no catálogo KEV da CISA, ou 0,41% do total — está em linha com a média geral do catálogo, indicando que o risco de exploração confirmada não foge do padrão da indústria, embora 94 falhas de severidade crítica representem uma superfície de ataque relevante para equipes de segurança que dependem de componentes Qualcomm em ambientes móveis, automotivos ou de IoT. A CVE mais perigosa atualmente em exploração ativa, CVE-2020-11261, apresenta EPSS de 0,0177, sugerindo probabilidade de exploração adicional relativamente baixa no curto prazo, mas sua presença no KEV exige atenção imediata em qualquer inventário de ativos afetados. O surgimento de 49 novas CVEs nos últimos 90 dias e a disponibilidade de PoCs públicas para 3 vulnerabilidades reforçam a necessidade de ciclos contínuos de atualização de firmware e monitoramento ativo de patches liberados pelo fabricante.

CVE-2018-11980—When a fake broadcast/multicast 11w rmf without mmie received, since no proper length check in wma_process_bip, buffer overflow will happen EPSS 0.2%CVE-2020-11309—Use after free in GPU driver while mapping the user memory to GPU memory due to improper check of referenced memory in Snapdragon Auto, SnapEPSS 0.2%CVE-2020-11180—Out of bound access in computer vision control due to improper validation of command length before processing it in Snapdragon Auto, SnapdraEPSS 0.2%CVE-2020-11185—Out of bound issue in WLAN driver while processing vdev responses from firmware due to lack of validation of data received from firmware in EPSS 0.2%CVE-2018-11894—In all android releases (Android for MSM, Firefox OS for MSM, QRD Android) from CAF using the linux kernel, while processing preferred netwoEPSS 0.2%CVE-2018-11869—In all android releases (Android for MSM, Firefox OS for MSM, QRD Android) from CAF using the linux kernel, lack of length validation check EPSS 0.2%CVE-2018-11868—In all android releases (Android for MSM, Firefox OS for MSM, QRD Android) from CAF using the linux kernel, lack of length validation check EPSS 0.2%CVE-2017-18124—During secure boot, addition is performed on uint8 ptrs which led to overflow issue in Small Cell SoC, Snapdragon Automobile, Snapdragon MobEPSS 0.2%CVE-2026-25262MEDIUMWrite-what-where Condition in Primary BootloaderEPSS 0.2%CVE-2025-47403MEDIUMBuffer Over-read in WLAN FirmwareEPSS 0.2%CVE-2020-3674—Information can leak into userspace due to improper transfer of data from kernel to userspace in Snapdragon Auto, Snapdragon Compute, SnapdrEPSS 0.2%CVE-2018-5911—Buffer overflow in WLAN function due to improper check of buffer size before copying in Snapdragon Auto, Snapdragon Consumer IOT, SnapdragonEPSS 0.2%CVE-2025-47401MEDIUMBuffer Over-read in WLAN HALEPSS 0.2%CVE-2018-13913—Improper validation of array index can lead to unauthorized access while processing debugFS in Snapdragon Auto, Snapdragon Consumer IOT, SnaEPSS 0.2%CVE-2019-2264—Null pointer dereference occurs for channel context while opening glink channel in Snapdragon Auto, Snapdragon Consumer IOT, Snapdragon MobiEPSS 0.2%CVE-2018-5830—While processing the HTT_T2H_MSG_TYPE_MGMT_TX_COMPL_IND message, a buffer overflow can potentially occur in Android releases from CAF using EPSS 0.2%CVE-2019-2235—Buffer overflow occurs when emulated RPMB is used due to sector size assumptions in the TA rollback protection logic. in Snapdragon Auto, SnEPSS 0.2%CVE-2019-14104—Slab-out-of-bounds access can occur if the context pointer is invalid due to lack of null check on pointer before accessing it in SnapdragonEPSS 0.2%CVE-2023-43537MEDIUMBuffer Over-read in WLAN HostEPSS 0.2%CVE-2018-5918—Possible buffer overflow in DRM Trusted application due to lack of check function return values in Snapdragon Automobile, Snapdragon Mobile EPSS 0.2%