Skip to main content
VulnerabilityPublished Updated

CVE-2025-20662: MediaTek MT9972 · Out-of-bounds Read

Affects MediaTek MT9972Source CVE Database V5

0

Not known to be exploited · CVSS 6.7 Medium.

Data as of 26 Oct 2026, 12:29 UTC

CVSS 3.1 base score
6.7Medium
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:H/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 7 Apr 2025

  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 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
MediaTek, Inc. MT9972Affected
  • =14.0
Fixed in–

AI-suggested

To mitigate CVE-2025-20662, organizations should: 1) Monitor MediaTek's official channels for the release of security patches corresponding to Patch ID DTV04428276 and apply them promptly to affected devices. 2) Restrict local access to devices running the MT9972 chipset by enforcing strict physical security and limiting administrative privileges to trusted personnel only. 3) Employ runtime protection mechanisms such as application sandboxing and integrity monitoring to detect anomalous behavior indicative of exploitation attempts. 4) Use mobile device management (MDM) solutions to enforce security policies and ensure devices are updated regularly. 5) Conduct regular security audits and vulnerability assessments focusing on privilege escalation vectors within the device environment. 6) For environments where patching is delayed, consider deploying compensating controls such as disabling or restricting PlayReady TA functionality if feasible. 7) Educate users and administrators about the risks of privilege escalation and the importance of maintaining strict access controls. These steps go beyond generic advice by emphasizing proactive patch management, access restriction, and runtime detection tailored to the specific nature of this vulnerability.

Description

In PlayReady TA, there is a possible out of bounds read 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: DTV04428276; Issue ID: MSV-3184.

References

Community reviews

Loading reviews…