# CVE-2025-20656: Memory corruption in MT6781, MT6789, MT6835, MT6855, MT6878, MT6879, MT6886, MT6895, MT6897, MT6983, MT6985, MT6989, MT6990, MT8196, MT8370, MT8390

> A missing bounds check in MediaTek Display Audio allows local attackers with physical access to escalate privileges via out-of-bounds write.

- **Severity:** Medium 6.8 (`CVSS:3.1/AV:P/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:** Yes
- **Published:** 7 Apr 2025
- **Updated:** 7 Apr 2025
- **Also known as:** A-393950961, ASB-A-393950961, GHSA-6vqr-8xjq-ghqg, M-ALPS09625423

## What is CVE-2025-20656?

CVE-2025-20656 is a medium-severity memory corruption vulnerability in Google Android, published on 7 Apr 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In DA, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of privilege, if an attacker has physical access to the device, with no additional execution privileges needed. User interaction is not needed for exploitation. Patch ID: ALPS09625423; Issue ID: MSV-3033.

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

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

It affects 20 products.


Products: Google Android, Linuxfoundation Yocto, Mediatek Mt6781, Mediatek Mt6789, Mediatek Mt6835, Mediatek Mt6855, Mediatek Mt6878, Mediatek Mt6879, Mediatek Mt6886, Mediatek Mt6895, Mediatek Mt6897, Mediatek Mt6983, Mediatek Mt6985, Mediatek Mt6989, Mediatek Mt6990, Mediatek Mt8196, Mediatek Mt8370, Mediatek Mt8390, Openwrt Openwrt, Rdkcentral Rdk-B.

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

Apply the vendor's patch.

## Is CVE-2025-20656 being exploited?

There is no known exploitation of CVE-2025-20656 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-2025-20656 and fix it if it is affected.

What it is: CVE-2025-20656 is a medium-severity memory corruption vulnerability in Google Android, published on 7 Apr 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-20656 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-2025-20656/ (Markdown: https://insights.sbomify.com/CVE-2025-20656/index.md)
```

## Sources

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

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