CVE-2018-11955: Critical severity android vulnerability
Lack of check on length of reason-code fetched from payload may lead driver access the memory not allocated to the frame and results in out of bound read in Snapdragon Auto, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon IoT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables in MDM9150, MDM9206, MDM9607, MDM9640, MDM9650, MSM8909W, MSM8996AU, QCA6174A, QCA6574AU, QCA9377, QCA9379, QCS405, QCS605, Qualcomm 215, SD 210/SD 212/SD 205, SD 425, SD 427, SD 430, SD 435, SD 439 / SD 429, SD 450, SD 600, SD 615/16/SD 415, SD 625, SD 632, SD 636, SD 650/52, SD 665, SD 712 / SD 710 / SD 670, SD 730, SD 820, SD 820A, SD 835, SD 845 / SD 850, SD 855, SDM439, SDM660, SDX20, SDX24
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2018-11955?
CVE-2018-11955 is classified as a medium severity vulnerability due to the potential for out-of-bounds read that could impact system stability.
How do I fix CVE-2018-11955?
To fix CVE-2018-11955, ensure that you update the affected Qualcomm firmware to the latest version that mitigates this vulnerability.
Which devices are affected by CVE-2018-11955?
CVE-2018-11955 affects devices utilizing Qualcomm Snapdragon chipsets, including various models of Android smartphones and Qualcomm IoT devices.
Can CVE-2018-11955 lead to data loss?
While CVE-2018-11955 primarily poses a risk of system instability, it may indirectly lead to data loss under certain circumstances of exploitation.
Is CVE-2018-11955 a remote code execution vulnerability?
CVE-2018-11955 is not classified as a remote code execution vulnerability; it primarily results in memory access issues.