First published: Mon Mar 02 2020(Updated: )
Stack buffer overflow due to instance id is misplaced inside definition of hardware accelerated effects in makefile in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Mobile in APQ8053, APQ8098, MDM9607, MDM9640, MSM8998, QCS605, SC8180X, SDM439, SDM630, SDM636, SDM660, SDM845, SDX24, SDX55, SM6150, SM7150, SM8150, SXR1130
Credit: product-security@qualcomm.com
Affected Software | Affected Version | How to fix |
---|---|---|
Android | ||
Qualcomm APQ8053 | ||
Qualcomm APQ8053 Firmware | ||
Qualcomm 8098 Firmware | ||
Qualcomm APQ8098 | ||
Qualcomm MD9607 Firmware | ||
Qualcomm MDM9607 firmware | ||
Qualcomm MDM9640 Firmware | ||
Qualcomm MDM9640 Firmware | ||
Qualcomm MSM8998 | ||
Qualcomm 8998 | ||
Qualcomm QCS605 | ||
Qualcomm QCS605 Firmware | ||
qualcomm SC8180X firmware | ||
Qualcomm SC8180X | ||
Qualcomm SDM439 Firmware | ||
Qualcomm SDM439 Firmware | ||
Qualcomm SDM630 | ||
Qualcomm SDM630 Firmware | ||
Qualcomm SD 636 Firmware | ||
Qualcomm SDM636 Firmware | ||
Qualcomm SD660 Firmware | ||
Qualcomm Snapdragon 660 | ||
Qualcomm SDA/SDM845 Firmware | ||
Qualcomm Snapdragon 845 | ||
Qualcomm SDX24 | ||
Qualcomm SDX24 | ||
Qualcomm SDX55M Firmware | ||
Qualcomm SDX55 Firmware | ||
Qualcomm SM6150P firmware | ||
Qualcomm SM6150P | ||
qualcomm SM7150P firmware | ||
qualcomm SM7150 firmware | ||
Qualcomm SM8150P Firmware | ||
Qualcomm SM8150 Fusion | ||
Qualcomm SXR1130 | ||
Qualcomm SXR1130 Firmware |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2019-10569 is classified as a critical severity vulnerability due to the potential for remote code execution.
To fix CVE-2019-10569, you should apply the latest firmware updates provided by Qualcomm for the affected devices.
CVE-2019-10569 affects several Qualcomm Snapdragon chipsets including APQ8053, APQ8098, MSM8998, and others.
CVE-2019-10569 is a stack buffer overflow vulnerability that can lead to arbitrary code execution.
As of now, there is no public information indicating active exploitation of CVE-2019-10569.