Skip to main content
CVE-2025-20801VulnerabilityPublished Updated

CVE-2025-20801: MediaTek chipset · Double Free

Affects MediaTek chipsetSource CVE Database V5

0

Not known to be exploited · CVSS 7.0 High.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score
7.0High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.05% 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:H/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-26.

What to do

Affected software

ProductAffectedFixed in
MediaTek, Inc.MediaTek chipsetAffected
  • =MT6878
  • =MT6897
  • =MT6899
  • =MT6985
  • =MT6989
  • =MT6991
  • =MT6993
  • =MT8792
  • =MT8796
  • =MT8798
Fixed in–

AI-suggested

To mitigate CVE-2025-20801, organizations and device manufacturers should prioritize deploying the official patch ALPS10251210 provided by MediaTek. Device firmware and operating system updates incorporating this patch must be applied promptly. For environments where patching may be delayed, implementing strict access controls to limit local system privileges can reduce exploitation risk. Monitoring for unusual local privilege escalation attempts and memory corruption indicators on devices with affected chipsets is advisable. Developers should review and harden code handling memory allocation and concurrency in similar components to prevent race conditions and double free errors. Additionally, employing runtime protections such as memory corruption mitigations (e.g., heap canaries, address space layout randomization) can reduce exploitation success. Vendors should communicate with customers about the vulnerability and remediation steps to ensure timely updates. Network segmentation and endpoint security controls can further limit attacker movement if devices are compromised.

Description

In seninf, there is a possible memory corruption due to a race condition. 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: ALPS10251210; Issue ID: MSV-4926.

References

Community reviews

Loading reviews…