CVE-2020-3619: Race Condition
u'Non-secure memory is touched multiple times during TrustZone\u2019s execution and can lead to privilege escalation or memory corruption' in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wired Infrastructure and Networking in APQ8009, APQ8017, APQ8053, APQ8098, IPQ8074, Kamorta, MDM9150, MDM9206, MDM9607, MDM9650, MSM8905, MSM8909, MSM8917, MSM8920, MSM8937, MSM8940, MSM8953, MSM8998, QCA8081, QCS404, QCS605, QCS610, QM215, Rennell, SA415M, SC7180, SDA660, SDA845, SDM429, SDM439, SDM450, SDM630, SDM632, SDM636, SDM660, SDM670, SDM710, SDM845, SDM850, SDX24, SM6150, SM7150, SM8150, SXR1130
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2020-3619?
CVE-2020-3619 has a severity rating that generally indicates a potential for privilege escalation or memory corruption.
How do I fix CVE-2020-3619?
To fix CVE-2020-3619, update to the latest firmware version provided by Qualcomm.
Which devices are affected by CVE-2020-3619?
CVE-2020-3619 affects various Qualcomm Snapdragon chips, including APQ8009, APQ8017, and others listed in the CVE descriptions.
What are the potential risks of CVE-2020-3619?
The potential risks of CVE-2020-3619 include unauthorized access to system resources and potential application crashes.
Is there a workaround for CVE-2020-3619?
Currently, the recommended method to mitigate CVE-2020-3619 is to apply the necessary firmware updates rather than relying on a workaround.