# CVE-2015-9148: Integer overflow in Snapdragon Automobile, Snapdragon Mobile

> An integer overflow in Qualcomm Snapdragon Diag command registration allows buffer overflow, potentially enabling code execution or privilege escalation on affected devices.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Apr 2018
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-gjmh-h963-w763

## What is CVE-2015-9148?

CVE-2015-9148 is a critical vulnerability in Qualcomm Mdm9625 Firmware, published on 18 Apr 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In Android before 2018-04-05 or earlier security patch level on Qualcomm Snapdragon Automobile and Snapdragon Mobile MDM9625, MDM9635M, MDM9640, MDM9645, MDM9650, MDM9655, SD 400, SD 425, SD 430, SD 450, SD 600, SD 617, SD 625, SD 650/52, SD 800, SD 808, SD 810, SD 820, SD 820A, SD 835, SD 845, SD 850, and SDX20, in the Diag User-PD command registration function, a length variable used during buffer allocation is not checked, so if it is very large, an integer overflow followed by a buffer overflow occurs.

Weakness: CWE-190 (Integer Overflow or Wraparound), CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2015-9148?

It affects 24 products.


Products: Qualcomm Mdm9625 Firmware, Qualcomm Mdm9635m Firmware, Qualcomm Mdm9640 Firmware, Qualcomm Mdm9645 Firmware, Qualcomm Mdm9650 Firmware, Qualcomm Mdm9655 Firmware, Qualcomm Sd 400 Firmware, Qualcomm Sd 425 Firmware, Qualcomm Sd 430 Firmware, Qualcomm Sd 450 Firmware, Qualcomm Sd 600 Firmware, Qualcomm Sd 617 Firmware, Qualcomm Sd 625 Firmware, Qualcomm Sd 650 Firmware, Qualcomm Sd 652 Firmware, Qualcomm Sd 800 Firmware, Qualcomm Sd 808 Firmware, Qualcomm Sd 810 Firmware, Qualcomm Sd 820 Firmware, Qualcomm Sd 820a Firmware and 4 more.

## How do I fix CVE-2015-9148?

No fix has been published for CVE-2015-9148 yet. Limit exposure of the affected software until one is available.

## Is CVE-2015-9148 being exploited?

There is no known exploitation of CVE-2015-9148 in the wild and no public exploit code.

## Other vulnerabilities in Qualcomm Mdm9625 Firmware

- [CVE-2014-10039](https://insights.sbomify.com/CVE-2014-10039/): Memory corruption in Snapdragon Mobile (critical 9.8)
- [CVE-2015-9108](https://insights.sbomify.com/CVE-2015-9108/): Memory corruption in Snapdragon Automobile, Snapdragon Mobile (critical 9.8)
- [CVE-2015-9109](https://insights.sbomify.com/CVE-2015-9109/): Null dereference in Snapdragon Automobile, Snapdragon Mobile (critical 9.8)
- [CVE-2015-9111](https://insights.sbomify.com/CVE-2015-9111/): Null dereference in Snapdragon Automobile, Snapdragon Mobile (critical 9.8)
- [CVE-2015-9112](https://insights.sbomify.com/CVE-2015-9112/): Memory corruption in Snapdragon Automobile, Snapdragon Mobile (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-9148 and fix it if it is affected.

What it is: CVE-2015-9148 is a critical vulnerability in Qualcomm Mdm9625 Firmware, published on 18 Apr 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2015-9148 in the wild and no public exploit code.

Affected product: Qualcomm Mdm9625 Firmware. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2015-9148/ (Markdown: https://insights.sbomify.com/CVE-2015-9148/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2015-9148
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2015-9148
- OSV: https://osv.dev/vulnerability/CVE-2015-9148

---
From sbomify Insights: https://insights.sbomify.com/CVE-2015-9148/
Summaries are generated and may contain mistakes; the official description above is the record.