# CVE-2025-59600: Buffer Over-read in Graphics

> A buffer over-read in Qualcomm Snapdragon graphics allows attackers to cause memory corruption, potentially leading to code execution or denial of service.

- **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:** Yes
- **Published:** 2 Mar 2026
- **Updated:** 3 Mar 2026
- **Also known as:** 4249775, A-465462602, ASB-A-465462602, GHSA-hjhm-8jgq-5frf

## What is CVE-2025-59600?

CVE-2025-59600 is a high-severity memory corruption vulnerability in Qualcomm Ar8031 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 adding user-supplied data without checking available buffer space.

Weakness: CWE-126 (Buffer Over-read)

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

It affects 164 products.


Products: Qualcomm Ar8031 Firmware, Qualcomm Ar8035 Firmware, Qualcomm Csra6620 Firmware, Qualcomm Csra6640 Firmware, Qualcomm Fastconnect 6200 Firmware, Qualcomm Fastconnect 6700 Firmware, Qualcomm Fastconnect 6900 Firmware, Qualcomm Fastconnect 7800 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 Mdm9628 Firmware, Qualcomm Milos Firmware, Qualcomm Monaco Iot Firmware and 144 more.

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

Apply the vendor's patch.

## Is CVE-2025-59600 being exploited?

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

## Other vulnerabilities in Qualcomm Ar8031 Firmware

- [CVE-2025-27038](https://insights.sbomify.com/CVE-2025-27038/): Qualcomm Multiple Chipsets Use-After-Free (high 7.5, exploited in the wild)
- [CVE-2022-25729](https://insights.sbomify.com/CVE-2022-25729/): Improper Input Validation in MODEM (critical 9.8)
- [CVE-2022-25727](https://insights.sbomify.com/CVE-2022-25727/): Memory corruption in Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Voice & Music (critical 9.8)
- [CVE-2021-30285](https://insights.sbomify.com/CVE-2021-30285/): Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Voice & Music, Snapdragon Wired Infrastructure and Networking (critical 9.3)
- [CVE-2021-30275](https://insights.sbomify.com/CVE-2021-30275/): Integer overflow in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Voice & Music, Snapdragon Wired Infrastructure and Networking (critical 9.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-59600 is a high-severity memory corruption vulnerability in Qualcomm Ar8031 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-59600 in the wild and no public exploit code.

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

## Sources

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

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