CVE-2025-20763: MediaTek MT6833, MT6835, MT6853, MT6855, MT6877, MT6878, MT6879, MT6883, MT6885, MT6886, MT6889, MT6893, MT6895, MT6897, MT6899, MT6983, MT6985, MT6989, MT6991, MT8196, MT8676, MT8678, MT8792, MT8793, MT8796, MT8873, MT8893 · Out-of-bounds Write
Affects MediaTek MT6833, MT6835, MT6853, MT6855, MT6877, MT6878, MT6879, MT6883, MT6885, MT6886, MT6889, MT6893, MT6895, MT6897, MT6899, MT6983, MT6985, MT6989, MT6991, MT8196, MT8676, MT8678, MT8792, MT8793, MT8796, MT8873, MT8893Source CVE Database V5
Not known to be exploited · CVSS 7.8 High.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.08% chance of exploitation in 30 days – higher than 0% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 2 Dec 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| MediaTek, Inc. MT6833, MT6835, MT6853, MT6855, MT6877, MT6878, MT6879, MT6883, MT6885, MT6886, MT6889, MT6893, MT6895, MT6897, MT6899, MT6983, MT6985, MT6989, MT6991, MT8196, MT8676, MT8678, MT8792, MT8793, MT8796, MT8873, MT8893 | Affected
| Fixed in– |
AI-suggested
To mitigate CVE-2025-20763, organizations and device manufacturers should prioritize applying the official MediaTek patch ALPS10267218 as soon as it becomes available. Device vendors should expedite firmware and OS updates incorporating this patch to end-users. Until patches are deployed, enforcing strict privilege separation and minimizing the number of processes running with System privileges can reduce exploitation risk. Employ runtime protections such as memory protection mechanisms (e.g., DEP, ASLR) where supported by the device to limit the impact of out-of-bounds writes. Security teams should monitor for unusual local privilege escalation attempts on devices with affected chipsets. For enterprise environments, consider restricting installation of untrusted applications and enforcing mobile device management policies that limit privilege escalation vectors. Additionally, vendors should conduct thorough code audits focusing on bounds checking in low-level firmware components to prevent similar vulnerabilities. End-users should be educated to update devices promptly and avoid rooting or granting unnecessary privileges to applications.
Description
In mmdvfs, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of privilege if a malicious actor has already obtained the System privilege. User interaction is not needed for exploitation. Patch ID: ALPS10267218; Issue ID: MSV-5032.