dbcve.org
Mdm9206 FirmwareOperating system · Qualcomm

CVE-2015-9129

CRITICAL · 9.8 CVSS v3.0 Published 2018-04-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
In Android before 2018-04-05 or earlier security patch level on Qualcomm Snapdragon Automobile, Snapdragon Mobile, and Snapdragon Wear MDM9206, MDM9650, MSM8909W, SD 210/SD 212/SD 205, SD 410/12, SD 425, SD 430, SD 450, SD 615/16/SD 415, SD 617, SD 625, SD 650/52, SD 808, SD 810, SD 820, SD 820A, SD 835, SD 845, and SD 850, if the size parameter passed to TZ_PR_CMD_CONTENT_SET_PROP is small, an integer underflow occurs.

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

Integer underflow vulnerability in Qualcomm TrustZone (TZ) when processing the TZ_PR_CMD_CONTENT_SET_PROP command with a small size parameter. This allows memory corruption in the secure world, potentially enabling arbitrary code execution with the highest privileges, bypassing all Android application sandboxing and security boundaries.

MitigationApply the April 2018 Android security patch or later, which contains the fix for this TrustZone vulnerability. For end-of-life devices that cannot receive patches, consider device replacement as no effective workaround exists.

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
Mdm9206 FirmwareOperating system
Affected:all versions
Mdm9650 FirmwareOperating system
Affected:all versions
Msm8909w FirmwareOperating system
Affected:all versions
Sd 210 FirmwareOperating system
Affected:all versions
Sd 212 FirmwareOperating system
Affected:all versions
Sd 205 FirmwareOperating system
Affected:all versions
Sd 410 FirmwareOperating system
Affected:all versions
Sd 412 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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/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 Qualcomm chipset model
    Check the device specifications or use commands like 'cat /proc/cpuinfo' or 'getprop ro.hardware' to determine the Qualcomm processor model
    Affected if The chipset is NOT one of: Mdm9206, Mdm9650, Msm8909w, Sd 210, Sd 212, Sd 205, Sd 410, or Sd 412
  2. Verify TrustZone is present
    Confirm the device uses Qualcomm TrustZone technology - check /proc/tee or consult device documentation for TrustZone/TEE presence
    Affected if TrustZone is not present on the device (non-Qualcomm or older architecture)
  3. Check TrustZone firmware version
    Query the TrustZone firmware version through manufacturer tools, diagnostic interfaces, or check the baseband/modem firmware version which typically includes TZ components
    Affected if The firmware version falls within the affected range: Mdm9206 (all versions), Mdm9650 (all versions), Msm8909w (all versions), Sd 210 (all versions), Sd 212 (all versions), Sd 205 (all versions), Sd 410 (all versions), Sd 412 (all versions)
  4. Confirm Android security patch level
    Check the Android security patch level via 'getprop ro.build.version.security_patch' - this indicates whether the April 2018 patch or later has been applied
    Affected if The security patch level is earlier than April 2018, indicating the vulnerability has not been patched

The device is affected if it uses any of the listed Qualcomm chipsets with TrustZone firmware versions that predate the April 2018 Android security patch.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the April 2018 Android security patch or later, which contains the fix for this TrustZone vulnerability. For end-of-life devices that cannot receive patches, consider device replacement as no effective workaround exists.

Recommended fix High confidence

Android security patch level 2018-04-05 or later (or the latest available security patch from the device manufacturer)

  1. Check current Android security patch level on affected device
  2. Update device to Android with security patch level dated 2018-04-05 or later
  3. If the device manufacturer no longer provides security updates, consider migrating to a device that receives regular monthly security patches
  4. For embedded/IoT devices using these Qualcomm Snapdragon chips, contact the device manufacturer for firmware updates that incorporate the security patch
Caveat Upgrading to a new Android version or device may cause compatibility issues with legacy applications or custom configurations; some older devices may not receive the update and require hardware replacement

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Mdm9206 Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation24.0 h
  • Testing16.0 h
  • Review / QA8.0 h
56.0 hours of engineering $9,760
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2015-9129 — 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-2015-9129 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