Skip to main content
CVE-2025-20798VulnerabilityPublished Updated

CVE-2025-20798: MediaTek chipset · Out-of-bounds Write

Affects MediaTek chipsetSource CVE Database V5

0

Not known to be exploited · CVSS 7.8 High.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
7.8High
How severe the flaw is on the 0–10 CVSS scale.
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:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 6 Jan 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
MediaTek, Inc.MediaTek chipsetAffected
  • =MT2718
  • =MT6765
  • =MT6768
  • =MT6781
  • =MT6833
  • =MT6835
  • =MT6853
  • =MT6855
  • =MT6877
  • =MT6879
  • =MT6893
  • =MT6985
  • =MT6989
  • =MT6991
  • =MT8186
  • =MT8188
  • =MT8196
  • =MT8367
  • =MT8391
  • =MT8676
  • =MT8678
  • =MT8696
  • =MT8766
  • =MT8768
  • =MT8781
  • =MT8786
  • =MT8792
  • =MT8793
  • =MT8796
  • =MT8873
  • =MT8883
  • =MT8893
Fixed in–

AI-suggested

1. Apply the official patch ALPS10315812 from MediaTek as soon as it becomes available for all affected chipset models. 2. Restrict local System-level access to trusted administrators only, minimizing the risk of an attacker gaining the initial required privileges. 3. Implement strict access controls and monitoring on devices using MediaTek chipsets to detect unusual privilege escalation attempts or memory corruption indicators. 4. Employ runtime protections such as memory protection mechanisms (e.g., DEP, ASLR) where supported by the device firmware to mitigate exploitation impact. 5. For organizations deploying IoT devices with these chipsets, ensure secure device onboarding and firmware update processes to quickly distribute patches. 6. Conduct regular security audits and vulnerability assessments focusing on local privilege escalation vectors. 7. Educate users and administrators about the risks of granting System-level access and encourage the use of least privilege principles.

Description

In battery, 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: ALPS10315812; Issue ID: MSV-5533.

References

Community reviews

Loading reviews…