# CVE-2026-21385: Qualcomm Multiple Chipsets Memory Corruption

> An integer overflow in Qualcomm Snapdragon graphics drivers allows memory corruption, potentially enabling code execution or privilege escalation on Android devices.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 3 Mar 2026 (CISA KEV)
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 2 Mar 2026
- **Updated:** 4 Mar 2026
- **Also known as:** 4387106, A-478214401, ASB-A-478214401, GHSA-wwwq-962j-m7x8

## What is CVE-2026-21385?

CVE-2026-21385 is a high-severity vulnerability in Qualcomm Apq8098 Firmware, published on 2 Mar 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Memory corruption while using alignments for memory allocation.

Weakness: CWE-190 (Integer Overflow or Wraparound)

## Which versions are affected by CVE-2026-21385?

It affects 237 products.


Products: Qualcomm 5g Fixed Wireless Access Platform Firmware, Qualcomm Apq8098 Firmware, Qualcomm Ar8031 Firmware, Qualcomm Ar8035 Firmware, Qualcomm C-V2x 9150 Firmware, Qualcomm Csra6620 Firmware, Qualcomm Csra6640 Firmware, Qualcomm Fastconnect 6200 Firmware, Qualcomm Fastconnect 6700 Firmware, Qualcomm Fastconnect 6800 Firmware, Qualcomm Fastconnect 6900 Firmware, Qualcomm Fastconnect 7800 Firmware, Qualcomm Flight Rb5 5g Platform Firmware, Qualcomm Fsm100 Platform Firmware, Qualcomm G1 Gen 1 Firmware, Qualcomm G2 Gen 1 Firmware, Qualcomm Iq-615 Firmware, Qualcomm Iq-8275 Firmware, Qualcomm Iq-8300 Firmware, Qualcomm Iq-9075 Firmware and 217 more.

## How do I fix CVE-2026-21385?

Apply the vendor's patch. US federal agencies must fix it by 24 Mar 2026.

## Is CVE-2026-21385 being exploited?

Yes. Attackers have exploited CVE-2026-21385 in the wild since at least 3 Mar 2026.

Public exploit code:

- A tool to scan Android devices for the recently exploited Qualcomm flaw CVE-2026-21385, providing a simple and efficient way to identify vulnerable devices and apply necessary patches. (github_poc): https://github.com/DaRkZ2012/qualcomm-vulnerability-scanner

## Other vulnerabilities in Qualcomm Apq8098 Firmware

- [CVE-2026-25268](https://insights.sbomify.com/CVE-2026-25268/): Stack-based Buffer Overflow in WLAN Host (high 8.8)
- [CVE-2025-47392](https://insights.sbomify.com/CVE-2025-47392/): Integer Overflow or Wraparound in GPS (high 8.8)
- [CVE-2026-25267](https://insights.sbomify.com/CVE-2026-25267/): Missing Authorization in Core (high 7.8)
- [CVE-2025-47379](https://insights.sbomify.com/CVE-2025-47379/): Use After Free in Automotive Audio (high 7.8)
- [CVE-2026-25275](https://insights.sbomify.com/CVE-2026-25275/): Buffer Over-read in WLAN Firmware (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-21385 and fix it if it is affected.

What it is: CVE-2026-21385 is a high-severity vulnerability in Qualcomm Apq8098 Firmware, published on 2 Mar 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2026-21385 in the wild since at least 3 Mar 2026.

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

## Sources

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

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