7.8
CWE
119 20
Advisory Published
CVE Published
Updated

CVE-2019-2250: Buffer Overflow

First published: Mon Apr 01 2019(Updated: )

Kernel can write to arbitrary memory address passed by user while freeing/stopping a thread in Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile in QCS605, SD 675, SD 712 / SD 710 / SD 670, SD 835, SD 845 / SD 850, SD 855, SD 8CX, SM7150, SXR1130

Credit: product-security@qualcomm.com

Affected SoftwareAffected VersionHow to fix
Android
Qualcomm ZZ QCS605 firmware
Qualcomm QCS605 Firmware
Qualcomm SD 675 Firmware
Qualcomm Snapdragon 675
Qualcomm Snapdragon 712 Firmware
Qualcomm Snapdragon 712
qualcomm sdm710 firmware
Qualcomm Snapdragon 710
Qualcomm SDM670 Firmware
Qualcomm SDM670
Qualcomm SD835 Firmware
Qualcomm Snapdragon 835
Qualcomm SDA845 Firmware
Qualcomm SD845
Qualcomm SD850 Firmware
Qualcomm SD850
Qualcomm SD855 Firmware
Qualcomm SD855 Firmware
Qualcomm SD 8cx firmware
Qualcomm Snapdragon 8cx
qualcomm SM7150 firmware
qualcomm SM7150 firmware
Qualcomm SXR1130
Qualcomm SXR1130 Firmware

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Frequently Asked Questions

  • What is the severity of CVE-2019-2250?

    CVE-2019-2250 has a high severity rating due to the potential for arbitrary memory writes impacting system stability and security.

  • How do I fix CVE-2019-2250?

    To fix CVE-2019-2250, apply the latest firmware updates from Qualcomm or your device manufacturer that address this vulnerability.

  • Which devices are affected by CVE-2019-2250?

    CVE-2019-2250 affects various Qualcomm Snapdragon processors, including QCS605, SD 675, SD 712, SD 710, SD 670, SD 835, SD 845, SD 850, SD 855, SD 8CX, SM7150, and SXR1130.

  • What are the potential impacts of CVE-2019-2250?

    The potential impacts of CVE-2019-2250 include denial of service and exploitation risks, as the kernel may be manipulated to write to unintended memory locations.

  • Is there a workaround for CVE-2019-2250?

    There are currently no known workarounds for CVE-2019-2250, so applying the appropriate firmware patch is necessary to mitigate the vulnerability.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203