dbcve.org
Mdm9615 FirmwareOperating system · Qualcomm

CVE-2015-9223

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 Mobile MDM9615, MDM9625, MDM9635M, SD 400, SD 600, and SD 800, a buffer overflow can occur when processing an audio buffer.

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 · moderate confidence

A buffer overflow vulnerability exists in the audio processing component of affected Qualcomm Snapdragon chipsets (MDM9615, MDM9625, MDM9635M, SD 400, SD 600, SD 800). The vulnerability allows potential remote code execution via a malformed audio buffer, with CVSS 9.8 indicating critical impact.

MitigationUpdate affected Android devices to the 2018-04-05 or later security patch level. If no update is available from the device OEM, consider device replacement or network-level mitigations to reduce exposure.

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
Mdm9615 FirmwareOperating system
Affected:all versions
Mdm9625 FirmwareOperating system
Affected:all versions
Mdm9635m FirmwareOperating system
Affected:all versions
Sd 400 FirmwareOperating system
Affected:all versions
Sd 600 FirmwareOperating system
Affected:all versions
Sd 800 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 device chipset model
    Check device specifications or use system information apps to determine the Qualcomm Snapdragon chipset model (e.g., MDM9615, MDM9625, MDM9635M, SD 400, SD 600, SD 800). This is typically found in the device About Phone section or by querying the baseband processor information.
    Affected if The chipset matches one of the following: MDM9615, MDM9625, MDM9635M, SD 400, SD 600, or SD 800.
  2. Verify audio processing component is active
    Confirm the device has an active audio subsystem. This is typically always enabled on mobile devices, but verify the audio service is running (e.g., check android.media.AudioService or equivalent process).
    Affected if The audio processing component is present and functional on the device.
  3. Confirm firmware version is present
    Check the baseband or firmware version information. Since all versions of the affected firmware are vulnerable, any firmware version present indicates exposure.
    Affected if Any firmware version is installed on an affected chipset model.

A device is affected if it contains any of the following Qualcomm Snapdragon chipsets: MDM9615, MDM9625, MDM9635M, SD 400, SD 600, or SD 800, regardless of firmware version.

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

Update affected Android devices to the 2018-04-05 or later security patch level. If no update is available from the device OEM, consider device replacement or network-level mitigations to reduce exposure.

Recommended fix High confidence

Android security patch level 2018-04-05 or later (contact device manufacturer for specific update)

  1. 1. Identify your device model and manufacturer (OEM) for the affected Qualcomm Snapdragon chip (MDM9615, MDM9625, MDM9635M, SD 400, SD 600, or SD 800)
  2. 2. Contact your device manufacturer to check if a security patch update after April 5, 2018 is available for your device
  3. 3. If available, apply the latest Android security patch level update from your device manufacturer
  4. 4. Verify the installed security patch level by going to Settings > About Phone > Security Patch Level and confirm it shows a date after 2018-04-05
  5. 5. If no update is available from your manufacturer, consider upgrading to a newer device that receives active security support
Caveat Older devices (SD 400, SD 600, SD 800) may no longer receive security updates from manufacturers; some may require device replacement

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

Fix this in Mdm9615 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA3.0 h
10.0 hours of engineering $1,820
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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