# CVE-2018-18318: Null dereference in n/a

> Attackers can crash Qiku 360 Phone N6 Pro devices via a crafted ioctl call to the mmcblk0rpmb kernel driver, causing a denial of service.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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:** 15 Oct 2018
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-4r9h-gpvv-2xg3

## What is CVE-2018-18318?

CVE-2018-18318 is a high-severity vulnerability in n/a, published on 15 Oct 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The /dev/block/mmcblk0rpmb driver kernel module on Qiku 360 Phone N6 Pro 1801-A01 devices allows attackers to cause a denial of service (NULL pointer dereference and device crash) via a crafted 0xc0d8b300 ioctl call.

Weakness: CWE-476 (NULL Pointer Dereference)

## Which versions are affected by CVE-2018-18318?

It affects 1 product.


Products: Qiku 360 Mobile Phone N6 Pro Firmware.

## How do I fix CVE-2018-18318?

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

## Is CVE-2018-18318 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-18318 and fix it if it is affected.

What it is: CVE-2018-18318 is a high-severity vulnerability in n/a, published on 15 Oct 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-2018-18318 in the wild and no public exploit code.

Affected product: n/a. 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-2018-18318/ (Markdown: https://insights.sbomify.com/CVE-2018-18318/index.md)
```

## Sources

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

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