CVE-2019-10486: Race Condition
Race condition due to the lack of resource lock which will be concurrently modified in the memcpy statement leads to out of bound access in Snapdragon Auto, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon IoT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables in APQ8009, APQ8017, APQ8053, APQ8096AU, APQ8098, MDM9206, MDM9207C, MDM9607, MDM9640, MDM9650, MSM8905, MSM8909W, MSM8939, MSM8953, MSM8996AU, MSM8998, Nicobar, QCN7605, QCS405, QCS605, QM215, SDA660, SDA845, SDM429, SDM439, SDM630, SDM632, SDM636, SDM660, SDM710, SDM845, SDX20, SDX24, SM6150, SM7150, SM8150
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2019-10486?
CVE-2019-10486 has a high severity due to its potential for out of bounds access and the implications of a race condition.
How do I fix CVE-2019-10486?
To fix CVE-2019-10486, apply the firmware updates provided by Qualcomm for the affected Snapdragon products.
What products are affected by CVE-2019-10486?
CVE-2019-10486 affects various Snapdragon platforms, including APQ8009, APQ8017, APQ8053, and others as detailed in the advisory.
What risks are associated with CVE-2019-10486?
The risks associated with CVE-2019-10486 include potential unauthorized access and system instability due to memory corruption.
Is additional information available for CVE-2019-10486?
Yes, additional information regarding CVE-2019-10486 can be found in Qualcomm's security bulletins.