# CVE-2025-27032: Improper Access Control Applied to Mirrored or Aliased Memory Regions in Hypervisor

> Memory corruption in Qualcomm Snapdragon hypervisor allows attackers to execute arbitrary code or escalate privileges during VM loading.

- **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:** 24 Sep 2025
- **Updated:** 26 Feb 2026
- **Also known as:** GHSA-xw4h-j9r2-r43w

## What is CVE-2025-27032?

CVE-2025-27032 is a high-severity memory corruption vulnerability in Qualcomm Aqt1000 Firmware, published on 24 Sep 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

memory corruption while loading a PIL authenticated VM, when authenticated VM image is loaded without maintaining cache coherency.

Weakness: CWE-1257 (Improper Access Control Applied to Mirrored or Aliased Memory Regions)

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

It affects 192 products.


Products: Qualcomm Aqt1000 Firmware, Qualcomm Ar8035 Firmware, Qualcomm Fastconnect 6200 Firmware, Qualcomm Fastconnect 6700 Firmware, Qualcomm Fastconnect 6800 Firmware, Qualcomm Fastconnect 6900 Firmware, Qualcomm Fastconnect 7800 Firmware, Qualcomm Qam8255p Firmware, Qualcomm Qam8295p Firmware, Qualcomm Qam8620p Firmware, Qualcomm Qam8650p Firmware, Qualcomm Qam8775p Firmware, Qualcomm Qamsrv1h Firmware, Qualcomm Qamsrv1m Firmware, Qualcomm Qca6174a Firmware, Qualcomm Qca6310 Firmware, Qualcomm Qca6335 Firmware, Qualcomm Qca6391 Firmware, Qualcomm Qca6420 Firmware, Qualcomm Qca6421 Firmware and 172 more.

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

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

## Is CVE-2025-27032 being exploited?

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

## Other vulnerabilities in Qualcomm Aqt1000 Firmware

- [CVE-2025-21479](https://insights.sbomify.com/CVE-2025-21479/): Qualcomm Multiple Chipsets Incorrect Authorization (high 8.6, exploited in the wild)
- [CVE-2025-21480](https://insights.sbomify.com/CVE-2025-21480/): Qualcomm Multiple Chipsets Incorrect Authorization (high 8.6, exploited in the wild)
- [CVE-2023-28562](https://insights.sbomify.com/CVE-2023-28562/): Buffer Copy Without Checking Size of Input in QESL (critical 9.8)
- [CVE-2022-40514](https://insights.sbomify.com/CVE-2022-40514/): Buffer copy without checking size of input in WLAN Firmware (critical 9.8)
- [CVE-2022-22096](https://insights.sbomify.com/CVE-2022-22096/): Memory corruption in Snapdragon Connectivity, Snapdragon Mobile (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-27032 is a high-severity memory corruption vulnerability in Qualcomm Aqt1000 Firmware, published on 24 Sep 2025. 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-27032 in the wild and no public exploit code.

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

## Sources

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

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