# CVE-2018-11263: Memory corruption in Android for MSM, Firefox OS for MSM, QRD Android

> An out-of-bounds write in the Qualcomm Android kernel allows attackers to execute arbitrary code or escalate privileges via crafted firmware responses.

- **Severity:** High 8.8 (`CVSS:3.0/AV:A/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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Sep 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-9p6f-69v3-qj46

## What is CVE-2018-11263?

CVE-2018-11263 is a high-severity memory corruption vulnerability in Google Android, published on 6 Sep 2018. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In all Android releases (Android for MSM, Firefox OS for MSM, QRD Android) from CAF using the Linux kernel, radio_id is received from the FW and is used to access the buffer to copy the radio stats received for each radio from FW. If the radio_id received from the FW is greater than or equal to maximum, an OOB write will occur. On supported Google Pixel and Nexus devices, this has been addressed in security patch level 2018-08-05.

Weakness: CWE-129 (Improper Validation of Array Index)

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

It affects 1 product.


Products: Google Android.

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

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

## Is CVE-2018-11263 being exploited?

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

## Other vulnerabilities in Google Android

- [CVE-2026-58704](https://insights.sbomify.com/CVE-2026-58704/): Google Pixel Improper Authorization (high 8.8, exploited in the wild)
- [CVE-2025-48543](https://insights.sbomify.com/CVE-2025-48543/): Android Runtime Use-After-Free (high 8.8, exploited in the wild)
- [CVE-2023-35674](https://insights.sbomify.com/CVE-2023-35674/): Android Framework Privilege Escalation (high 8.8, exploited in the wild)
- [CVE-2025-48595](https://insights.sbomify.com/CVE-2025-48595/): Android Framework Integer Overflow (high 8.4, exploited in the wild)
- [CVE-2024-32896](https://insights.sbomify.com/CVE-2024-32896/): Android Pixel Privilege Escalation (high 8.1, exploited in the wild)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-11263 is a high-severity memory corruption vulnerability in Google Android, published on 6 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-2018-11263 in the wild and no public exploit code.

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

## Sources

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

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