CVE-2018-5914: Out-of-bounds Read

Published Sep 4, 2018
·
Updated

Improper input validation in TZ led to array out of bound in TZ function while accessing the peripheral details using the incoming data in Snapdragon Mobile, Snapdragon Wear version MDM9206, MDM9607, MDM9650, SD 210/SD 212/SD 205, SD 425, SD 430, SD 450, SD 625, SD 650/52, SD 835, SDA660.

Affected Software

29 affected components
Google Android
Qualcomm Mdm9206 Firmware
Qualcomm MDM9206
Qualcomm Mdm9607 Firmware
Qualcomm MDM9607
Qualcomm Mdm9650 Firmware
Qualcomm MDM9650
Qualcomm Sd 210 Firmware
Qualcomm SD 210
Qualcomm Sd 212 Firmware
Qualcomm SD 212
Qualcomm Sd 205 Firmware
Qualcomm SD 205
Qualcomm Sd 425 Firmware
Qualcomm SD 425
Qualcomm Sd 430 Firmware
Qualcomm SD 430
Qualcomm Sd 450 Firmware
Qualcomm SD 450
Qualcomm Sd 625 Firmware
Qualcomm SD 625
Qualcomm Sd 650 Firmware
Qualcomm SD 650
Qualcomm Sd 652 Firmware
Qualcomm Sd 652
Qualcomm Sd 835 Firmware
Qualcomm SD 835
Qualcomm Sda660 Firmware
Qualcomm SDA660

Event History

Sep 4, 2018
CVE Published
via Android·12:00 AM
Data Sourced
via Android·12:00 AM
SeverityAffected Software
Oct 26, 2018
CVE Published
via MITRE·01:00 PM
Data Sourced
via MITRE·01:00 PM
DescriptionWeakness
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2018-5914?

CVE-2018-5914 has been classified with a medium severity level due to the potential for array out of bounds access.

2

How do I fix CVE-2018-5914?

To fix CVE-2018-5914, ensure that you update the affected firmware and software versions as provided by Qualcomm.

3

What systems are affected by CVE-2018-5914?

CVE-2018-5914 affects various Snapdragon Mobile and Snapdragon Wear versions, including MDM9206, MDM9607, and others.

4

What is the impact of CVE-2018-5914 on devices?

The impact of CVE-2018-5914 may lead to potential denial-of-service conditions due to improper input validation.

5

Is there a workaround for CVE-2018-5914?

Currently, there are no known effective workarounds for CVE-2018-5914 besides applying the necessary updates.

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.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203