Track vulnerabilities like this one. Sign up free to get alerted when software you use is affected.
7.8

Qualcomm firmware may overflow buffer and crash

CVE-2019-10496 · published 7 years ago
Summary

The firmware for several Qualcomm chipsets does not verify a value from a driver before storing it, which can cause data to overflow a memory area. This could lead to system instability or allow an attacker to execute code. Update the firmware to the latest version provided by Qualcomm to fix the issue.

What to do

The CVE record does not list a fixed version. Check the vendor's site or the advisory links below - a fix may already be released.

Affected software
VendorProductAffected versions
qualcomm msm8909w_firmware All versions
cpe:2.3:o:qualcomm:msm8909w_firmware:-:*:*:*:*:*:*:*
qualcomm msm8996au_firmware All versions
cpe:2.3:o:qualcomm:msm8996au_firmware:-:*:*:*:*:*:*:*
qualcomm qcs605_firmware All versions
cpe:2.3:o:qualcomm:qcs605_firmware:-:*:*:*:*:*:*:*
qualcomm qualcomm_215_firmware All versions
cpe:2.3:o:qualcomm:qualcomm_215_firmware:-:*:*:*:*:*:*:*
qualcomm sd_210_firmware All versions
cpe:2.3:o:qualcomm:sd_210_firmware:-:*:*:*:*:*:*:*
qualcomm sd_212_firmware All versions
cpe:2.3:o:qualcomm:sd_212_firmware:-:*:*:*:*:*:*:*
qualcomm sd_205_firmware All versions
cpe:2.3:o:qualcomm:sd_205_firmware:-:*:*:*:*:*:*:*
qualcomm sd_425_firmware All versions
cpe:2.3:o:qualcomm:sd_425_firmware:-:*:*:*:*:*:*:*
qualcomm sd_427_firmware All versions
cpe:2.3:o:qualcomm:sd_427_firmware:-:*:*:*:*:*:*:*
qualcomm sd_430_firmware All versions
cpe:2.3:o:qualcomm:sd_430_firmware:-:*:*:*:*:*:*:*
qualcomm sd_435_firmware All versions
cpe:2.3:o:qualcomm:sd_435_firmware:-:*:*:*:*:*:*:*
qualcomm sd_439_firmware All versions
cpe:2.3:o:qualcomm:sd_439_firmware:-:*:*:*:*:*:*:*
qualcomm sd_429_firmware All versions
cpe:2.3:o:qualcomm:sd_429_firmware:-:*:*:*:*:*:*:*
qualcomm sd_450_firmware All versions
cpe:2.3:o:qualcomm:sd_450_firmware:-:*:*:*:*:*:*:*
qualcomm sd_625_firmware All versions
cpe:2.3:o:qualcomm:sd_625_firmware:-:*:*:*:*:*:*:*
qualcomm sd_632_firmware All versions
cpe:2.3:o:qualcomm:sd_632_firmware:-:*:*:*:*:*:*:*
qualcomm sd_636_firmware All versions
cpe:2.3:o:qualcomm:sd_636_firmware:-:*:*:*:*:*:*:*
qualcomm sd_665_firmware All versions
cpe:2.3:o:qualcomm:sd_665_firmware:-:*:*:*:*:*:*:*
qualcomm sd_675_firmware All versions
cpe:2.3:o:qualcomm:sd_675_firmware:-:*:*:*:*:*:*:*
qualcomm sd_712_firmware All versions
cpe:2.3:o:qualcomm:sd_712_firmware:-:*:*:*:*:*:*:*
qualcomm sd_710_firmware All versions
cpe:2.3:o:qualcomm:sd_710_firmware:-:*:*:*:*:*:*:*
qualcomm sd_670_firmware All versions
cpe:2.3:o:qualcomm:sd_670_firmware:-:*:*:*:*:*:*:*
qualcomm sd_730_firmware All versions
cpe:2.3:o:qualcomm:sd_730_firmware:-:*:*:*:*:*:*:*
qualcomm sd_820_firmware All versions
cpe:2.3:o:qualcomm:sd_820_firmware:-:*:*:*:*:*:*:*
qualcomm sd_820a_firmware All versions
cpe:2.3:o:qualcomm:sd_820a_firmware:-:*:*:*:*:*:*:*
qualcomm sd_835_firmware All versions
cpe:2.3:o:qualcomm:sd_835_firmware:-:*:*:*:*:*:*:*
qualcomm sd_845_firmware All versions
cpe:2.3:o:qualcomm:sd_845_firmware:-:*:*:*:*:*:*:*
qualcomm sd_850_firmware All versions
cpe:2.3:o:qualcomm:sd_850_firmware:-:*:*:*:*:*:*:*
qualcomm sd_855_firmware All versions
cpe:2.3:o:qualcomm:sd_855_firmware:-:*:*:*:*:*:*:*
qualcomm sd_8cx_firmware All versions
cpe:2.3:o:qualcomm:sd_8cx_firmware:-:*:*:*:*:*:*:*
qualcomm sda660_firmware All versions
cpe:2.3:o:qualcomm:sda660_firmware:-:*:*:*:*:*:*:*
qualcomm sdm439_firmware All versions
cpe:2.3:o:qualcomm:sdm439_firmware:-:*:*:*:*:*:*:*
qualcomm sdm630_firmware All versions
cpe:2.3:o:qualcomm:sdm630_firmware:-:*:*:*:*:*:*:*
qualcomm sdm660_firmware All versions
cpe:2.3:o:qualcomm:sdm660_firmware:-:*:*:*:*:*:*:*
qualcomm snapdragon_high_med_2016_firmware All versions
cpe:2.3:o:qualcomm:snapdragon_high_med_2016_firmware:-:*:*:*:*:*:*:*
qualcomm sxr1130_firmware All versions
cpe:2.3:o:qualcomm:sxr1130_firmware:-:*:*:*:*:*:*:*
Original advisory text
Lack of checking a variable received from driver and populating in Firmware data structure leads to buffer overflow in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consu...
Lack of checking a variable received from driver and populating in Firmware data structure leads to buffer overflow in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables in MSM8909W, MSM8996AU, QCS605, Qualcomm 215, SD 210/SD 212/SD 205, SD 425, SD 427, SD 430, SD 435, SD 439 / SD 429, SD 450, SD 625, SD 632, SD 636, SD 665, SD 675, SD 712 / SD 710 / SD 670, SD 730, SD 820, SD 820A, SD 835, SD 845 / SD 850, SD 855, SD 8CX, SDA660, SDM439, SDM630, SDM660, Snapdragon_High_Med_2016, SXR1130
References
Fix within
Internet-facing 14 days
Internal At next upgrade
  • Not known to be exploited
  • Needs hands-on effort to exploit (estimated)
  • Gives an attacker full control (estimated)
Severity
7.8 High
Exploitation
<1% chance of attack within 30 days
Type
CWE-120Classic Buffer Overflow
Timeline
Published6 Nov 2019
Updated4 Nov 2026
First seen29 Sep 2026
Sources
CVE-2019-10496 · NVD
Track software like this
Free during beta