dbcve.org
Mdm9150 FirmwareOperating system · Qualcomm

CVE-2019-10498

HIGH · 7.8 CVSS v3.1 Published 2019-09-30
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Buffer overflow scenario if the client sends more than 5 io_vec requests to the server in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon IoT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables in MDM9150, MDM9206, MDM9607, MDM9640, MDM9650, MSM8909W, MSM8996AU, 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 615/16/SD 415, 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, SDA660, SDM439, SDM630, SDM660, SDX20, SDX24

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A buffer overflow vulnerability exists in Qualcomm Snapdragon processors where the server component fails to properly validate the number of io_vec requests received from clients. When a client sends more than 5 io_vec requests, the server does not enforce proper bounds checking, leading to potential memory corruption and code execution. This affects multiple Snapdragon chipset families used across automotive, compute, IoT, mobile, and wearable platforms.

MitigationThe vulnerability requires a firmware update from Qualcomm to address the improper bounds checking on io_vec requests. Device manufacturers must integrate the Qualcomm firmware patch and distribute updates to end-user devices. Network-level mitigations may be possible by limiting io_vec request rates or counts, but the definitive fix is the vendor-supplied firmware update.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Mdm9150 FirmwareOperating system
Affected:all versions
Mdm9206 FirmwareOperating system
Affected:all versions
Mdm9607 FirmwareOperating system
Affected:all versions
Mdm9640 FirmwareOperating system
Affected:all versions
Mdm9650 FirmwareOperating system
Affected:all versions
Msm8909w FirmwareOperating system
Affected:all versions
Msm8996au FirmwareOperating system
Affected:all versions
Qcs405 FirmwareOperating system
Affected:all versions

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the chipset model
    Check the device hardware specifications or system information to determine the Qualcomm Snapdragon chipset model (e.g., Mdm9150, Mdm9206, Mdm9607, Mdm9640, Mdm9650, Msm8909w, Msm8996au, or Qcs405)
    Affected if The chipset matches one of the affected models listed in the CVE (Mdm9150, Mdm9206, Mdm9607, Mdm9640, Mdm9650, Msm8909w, Msm8996au, or Qcs405)
  2. Determine the firmware version
    Access the device firmware information through manufacturer documentation, device settings, or diagnostic interfaces to identify the installed firmware version
    Affected if Firmware is present on any of the affected chipset models (all versions of the listed chipsets are vulnerable)
  3. Verify if the server component is exposed
    Check network configuration or service listings to determine if the io_vec handling server component is accessible from network interfaces or only isolated within the trusted execution environment
    Affected if The server component that processes io_vec requests is reachable from untrusted network paths or client-facing interfaces
  4. Look for indicators of anomalous io_vec activity
    Review system logs, network traffic logs, or security event logs for patterns of excessive io_vec requests or memory corruption indicators
    Affected if Logs show abnormal io_vec request patterns exceeding normal client behavior or memory corruption signatures
  5. Check for existing firmware update availability
    Consult the device manufacturer or Qualcomm to confirm if a firmware patch addressing CVE-2019-10498 has been released and applied
    Affected if No vendor-supplied firmware update addressing this vulnerability has been installed

A device is affected if it uses any of the listed Qualcomm Snapdragon chipset models (Mdm9150, Mdm9206, Mdm9607, Mdm9640, Mdm9650, Msm8909w, Msm8996au, or Qcs405) and the vulnerable server component is accessible, since all firmware versions of these chipsets are currently vulnerable.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

The vulnerability requires a firmware update from Qualcomm to address the improper bounds checking on io_vec requests. Device manufacturers must integrate the Qualcomm firmware patch and distribute updates to end-user devices. Network-level mitigations may be possible by limiting io_vec request rates or counts, but the definitive fix is the vendor-supplied firmware update.

Fix this in Mdm9150 Firmware Scoped from the published advisory
  • Consultation16.0 h
  • Implementation24.0 h
  • Testing32.0 h
  • Review / QA16.0 h
88.0 hours of engineering $15,200
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $24,320.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-10498 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-10498 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data