CVE-2019-10516: Critical severity Google Android vulnerability
Multiple read overflows in MM while decoding service accept,service reject,attach reject and MT detach in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon IoT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables in APQ8009, APQ8017, APQ8053, APQ8096, APQ8096AU, APQ8098, MDM9150, MDM9205, MDM9206, MDM9607, MDM9625, MDM9635M, MDM9640, MDM9645, MDM9650, MDM9655, MSM8905, MSM8909, MSM8909W, MSM8917, MSM8920, MSM8937, MSM8939, MSM8940, MSM8953, MSM8996AU, MSM8998, Nicobar, QCM2150, QCS605, QM215, SC8180X, SDA660, SDA845, SDM429, SDM439, SDM450, SDM630, SDM632, SDM636, SDM660, SDM670, SDM710, SDM845, SDM850, SDX20, SDX24, SDX55, SM6150, SM7150, SM8150, SXR1130
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2019-10516?
CVE-2019-10516 has been rated as having a high severity due to multiple read overflows that could lead to remote code execution or information disclosure.
What systems are affected by CVE-2019-10516?
CVE-2019-10516 affects various Qualcomm Snapdragon platforms, including but not limited to APQ8009, APQ8017, and several other models listed in the vulnerability details.
How do I fix CVE-2019-10516?
To fix CVE-2019-10516, users should update their devices to the latest firmware provided by Qualcomm or follow Android's security bulletin guidelines for available patches.
What types of devices are impacted by CVE-2019-10516?
Devices using Qualcomm Snapdragon processors in categories such as mobile, automotive, and IoT are impacted by CVE-2019-10516.
Is there a workaround for CVE-2019-10516?
Currently, there are no recommended workarounds for CVE-2019-10516; applying the available firmware updates is the best course of action.