dbcve.org
Mdm9625 FirmwareOperating system · Qualcomm

CVE-2015-9115

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 and Snapdragon Mobile MDM9625, SD 410/12, SD 425, SD 430, SD 450, SD 615/16/SD 415, SD 617, SD 625, SD 650/52, SD 820, and SD 820A, no address argument validation is performed on calls to the qsee_prng_getdata syscall.

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 missing address argument validation vulnerability exists in the qsee_prng_getdata syscall within the Qualcomm Secure Execution Environment (QSEE) kernel interface. The syscall, which retrieves pseudo-random number generator data from the secure element, does not validate the memory address provided by the caller before reading data, potentially allowing an attacker to read arbitrary kernel memory locations.

MitigationApply the Android security patch level from 2018-04-05 or later, which includes address validation in the qsee_prng_getdata syscall. This is an OEM-level fix delivered through system updates; individual app-level mitigations are not applicable.

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
Mdm9625 FirmwareOperating system
Affected:all versions
Sd 410 FirmwareOperating system
Affected:all versions
Sd 412 FirmwareOperating system
Affected:all versions
Sd 425 FirmwareOperating system
Affected:all versions
Sd 430 FirmwareOperating system
Affected:all versions
Sd 450 FirmwareOperating system
Affected:all versions
Sd 615 FirmwareOperating system
Affected:all versions
Sd 616 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 chipset model
    Check the device specifications or use a system info app to confirm the Qualcomm Snapdragon or MDM chipset matches one of the affected models: Mdm9625, Sd 410, Sd 412, Sd 425, Sd 430, Sd 450, Sd 615, or Sd 616
    Affected if The device uses any of the listed Qualcomm chipset models in the affected firmware list
  2. Check the Android security patch level
    Navigate to Settings > About Phone > Security patch level on the device, or run 'adb shell getprop ro.build.version.security_patch'
    Affected if The security patch level is earlier than 2018-04-05 or the field is empty or unpatched
  3. Verify the QSEE syscall version
    This requires access to the QSEE image or firmware binary. Analysts with firmware access can inspect the qsee_prng_getdata syscall implementation for address validation checks (e.g., check for bounds checking on the address pointer before the memory read operation)
    Affected if The syscall code lacks validation that the provided address falls within allowed memory regions before performing the read operation

A defender is affected if their device uses one of the listed Qualcomm chipsets AND has not received the 2018-04-05 or later Android security patch, since the patch contains the address validation fix for the qsee_prng_getdata syscall vulnerability.

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 Android security patch level from 2018-04-05 or later, which includes address validation in the qsee_prng_getdata syscall. This is an OEM-level fix delivered through system updates; individual app-level mitigations are not applicable.

Recommended fix High confidence

Android Security Patch Level 2018-04-05 or later (delivered via OEM firmware update)

  1. Verify the current Android security patch level on the affected device by going to Settings > About Phone > Security Patch Level
  2. Contact the device manufacturer (OEM) to obtain and apply the Android security update for April 2018 or later
  3. Install the security patch level 2018-04-05 or later on the affected device
  4. Verify the security patch level has been successfully updated to 2018-04-05 or later after the update
Caveat Security updates typically have minimal risk, but verify with OEM that the update is compatible with your specific device model

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

Fix this in Mdm9625 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing8.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,720
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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