# CVE-2025-47373: Out-of-bounds Write in Automotive

> An out-of-bounds write in Qualcomm Snapdragon firmware allows attackers to execute arbitrary code or escalate privileges via invalid buffer lengths.

- **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:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Mar 2026
- **Updated:** 2 Mar 2026
- **Also known as:** GHSA-x93w-8964-8vm7

## What is CVE-2025-47373?

CVE-2025-47373 is a high-severity memory corruption vulnerability in Qualcomm Ar8035 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 when accessing buffers with invalid length during TA invocation.

Weakness: CWE-787 (Out-of-bounds Write)

## Which versions are affected by CVE-2025-47373?

It affects 188 products.


Products: Qualcomm Ar8035 Firmware, Qualcomm Cologne Firmware, Qualcomm Fastconnect 6200 Firmware, Qualcomm Fastconnect 6700 Firmware, Qualcomm Fastconnect 6900 Firmware, Qualcomm Fastconnect 7800 Firmware, Qualcomm Fwa Gen 3 Ultra 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, Qualcomm Iq-9100 Firmware, Qualcomm Lemans Au Lgit Firmware, Qualcomm Lemansau Firmware, Qualcomm Milos Firmware, Qualcomm Monaco Iot Firmware, Qualcomm Netrani Firmware, Qualcomm Orne Firmware and 168 more.

## How do I fix CVE-2025-47373?

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

## Is CVE-2025-47373 being exploited?

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

## Other vulnerabilities in Qualcomm Ar8035 Firmware

- [CVE-2023-33106](https://insights.sbomify.com/CVE-2023-33106/): Qualcomm Multiple Chipsets Use of Out-of-Range Pointer Offset (high 8.4, exploited in the wild)
- [CVE-2024-45569](https://insights.sbomify.com/CVE-2024-45569/): Improper Validation of Array Index in WLAN Host Communication (critical 9.8)
- [CVE-2024-21473](https://insights.sbomify.com/CVE-2024-21473/): Improper Input Validation in WIN SON (critical 9.8)
- [CVE-2023-28582](https://insights.sbomify.com/CVE-2023-28582/): Buffer Copy Without Checking Size of Input in Data Modem (critical 9.8)
- [CVE-2023-43552](https://insights.sbomify.com/CVE-2023-43552/): Use After Free in WLAN Host Communication (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-47373 and fix it if it is affected.

What it is: CVE-2025-47373 is a high-severity memory corruption vulnerability in Qualcomm Ar8035 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: There is no known exploitation of CVE-2025-47373 in the wild and no public exploit code.

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

## Sources

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

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