CVE-2017-8252: Medium severity Google Android vulnerability
Kernel can inject faults in computations during the execution of TrustZone leading to information disclosure in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon IoT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables, Snapdragon Wired Infrastructure and Networking in IPQ4019, IPQ8074, MDM9150, MDM9206, MDM9607, MDM9615, MDM9635M, MDM9640, MDM9650, MDM9655, MSM8909W, MSM8996AU, QCA8081, QCS605, Qualcomm 215, SD 210/SD 212/SD 205, SD 410/12, SD 425, SD 427, SD 430, SD 435, SD 439 / SD 429, SD 450, SD 615/16/SD 415, SD 625, SD 632, SD 636, SD 650/52, SD 675, SD 712 / SD 710 / SD 670, SD 820, SD 820A, SD 835, SD 845 / SD 850, SD 855, SD 8CX, SDA660, SDM439, SDM630, SDM660, SDX20, SDX24, SM7150, SnapdragonHighMed2016, SXR1130
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2017-8252?
CVE-2017-8252 has a high severity rating, as it can lead to information disclosure during TrustZone execution.
How do I fix CVE-2017-8252?
The recommended fix for CVE-2017-8252 is to apply the security updates provided by the device manufacturer.
What software is affected by CVE-2017-8252?
CVE-2017-8252 affects various Qualcomm Snapdragon platforms, including Android devices utilizing Snapdragon technology.
What are the risks associated with CVE-2017-8252?
The risks associated with CVE-2017-8252 include potential information disclosure that could affect device security and user privacy.
Is there a workaround for CVE-2017-8252?
Currently, there are no known workarounds for CVE-2017-8252 other than applying the appropriate firmware updates.