CVE-2019-10600: Null Pointer Dereference
Use of local variable as argument to netlink CB callback goes out of it scope when callback triggered lead to invalid stack memory in Snapdragon Auto, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon IoT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables, Snapdragon Wired Infrastructure and Networking in APQ8009, APQ8017, APQ8053, APQ8096AU, APQ8098, IPQ4019, IPQ8064, IPQ8074, MDM9150, MDM9206, MDM9207C, MDM9607, MDM9650, MSM8909, MSM8909W, MSM8917, MSM8920, MSM8937, MSM8939, MSM8940, MSM8953, MSM8996AU, MSM8998, Nicobar, QCA6574AU, QCA8081, QCS405, QCS605, QM215, SA6155P, SDA845, SDM429, SDM439, SDM450, SDM630, SDM632, SDM636, SDM660, SDM670, SDM710, SDM845, SDX20, SDX24, SDX55, SM6150, SM7150, SM8150, SM8250, SXR1130, SXR2130
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2019-10600?
CVE-2019-10600 has been classified as critical due to its potential to corrupt memory and lead to arbitrary code execution.
How do I fix CVE-2019-10600?
To fix CVE-2019-10600, update your device firmware to the latest version provided by Qualcomm or your device manufacturer.
Which devices are affected by CVE-2019-10600?
CVE-2019-10600 affects a variety of Qualcomm Snapdragon platforms, including smartphones and IoT devices.
What types of exploits can be performed using CVE-2019-10600?
CVE-2019-10600 could potentially allow attackers to execute arbitrary code with elevated privileges due to memory corruption.
Is there a workaround for CVE-2019-10600 while waiting for a patch?
Currently, the best practice is to apply the official patch, as there are no known workarounds that effectively mitigate CVE-2019-10600.