# CVE-2017-18301: Null dereference in n/a

> A null pointer dereference in Qualcomm Snapdragon SoCs allows attackers to cause a system restart via a crafted IOCTL call.

- **Severity:** Medium 5.5 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Sep 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-g8pp-68w8-fg6c

## What is CVE-2017-18301?

CVE-2017-18301 is a medium-severity vulnerability in Qualcomm Mdm9607 Firmware, published on 20 Sep 2018. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In Small Cell SoC and Snapdragon (Automobile, Mobile, Wear) in version FSM9055, FSM9955, MDM9607, MDM9640, MDM9650, MSM8909W, SD 425, SD 427, SD 430, SD 435, SD 450, SD 617, SD 625, SD 650/52, SD 820, SD 820A, SD 835, SD 845, SDM630, SDM636, SDM660, SDX20, Snapdragon_High_Med_2016, providing the NULL argument of ICE regulator while processing create key IOCTL results in system restart.

Weakness: CWE-476 (NULL Pointer Dereference)

## Which versions are affected by CVE-2017-18301?

It affects 23 products.


Products: Qualcomm Fsm9055 Firmware, Qualcomm Fsm9955 Firmware, Qualcomm Mdm9607 Firmware, Qualcomm Mdm9640 Firmware, Qualcomm Mdm9650 Firmware, Qualcomm Msm8909w Firmware, Qualcomm Sd425 Firmware, Qualcomm Sd427 Firmware, Qualcomm Sd430 Firmware, Qualcomm Sd435 Firmware, Qualcomm Sd450 Firmware, Qualcomm Sd617 Firmware, Qualcomm Sd625 Firmware, Qualcomm Sd650 Firmware, Qualcomm Sd652 Firmware, Qualcomm Sd820 Firmware, Qualcomm Sd820a Firmware, Qualcomm Sd835 Firmware, Qualcomm Sd845 Firmware, Qualcomm Sdm630 Firmware and 3 more.

## How do I fix CVE-2017-18301?

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

## Is CVE-2017-18301 being exploited?

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

## Other vulnerabilities in Qualcomm Mdm9607 Firmware

- [CVE-2014-10052](https://insights.sbomify.com/CVE-2014-10052/): Information disclosure in Snapdragon Mobile, Snapdragon Wear, Small Cell SoC (critical 9.8)
- [CVE-2015-9138](https://insights.sbomify.com/CVE-2015-9138/): Memory corruption in Snapdragon Automobile, Snapdragon Mobile, Snapdragon Wear, Small Cell SoC (critical 9.8)
- [CVE-2015-9196](https://insights.sbomify.com/CVE-2015-9196/): Privilege escalation in Snapdragon Mobile, Small Cell SoC (critical 9.8)
- [CVE-2015-9224](https://insights.sbomify.com/CVE-2015-9224/): Memory corruption in Snapdragon Automobile, Snapdragon Mobile, Snapdragon Wear, Small Cell SoC (critical 9.8)
- [CVE-2016-10412](https://insights.sbomify.com/CVE-2016-10412/): Integer overflow in Small Cell SoC , Snapdragon Mobile, Snapdragon Wear (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-18301 and fix it if it is affected.

What it is: CVE-2017-18301 is a medium-severity vulnerability in Qualcomm Mdm9607 Firmware, published on 20 Sep 2018. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-18301 in the wild and no public exploit code.

Affected product: Qualcomm Mdm9607 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-2017-18301/ (Markdown: https://insights.sbomify.com/CVE-2017-18301/index.md)
```

## Sources

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

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