Skip to main content
VulnerabilityPublished Updated

CVE-2025-20672: MediaTek MT7902, MT7921, MT7922, MT7925, MT7927 · Heap Overflow

Affects MediaTek MT7902, MT7921, MT7922, MT7925, MT7927Source CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.6% chance of exploitation in 30 days – higher than 50% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 2 Jun 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

AI-suggested

To mitigate CVE-2025-20672, organizations should: 1) Monitor MediaTek and device vendor advisories closely and apply official patches or firmware updates as soon as they become available. 2) Restrict local user privileges to the minimum necessary to reduce the risk of local exploitation. 3) Implement strict access controls and endpoint protection to detect and prevent unauthorized code execution on devices with affected chipsets. 4) Disable or limit Bluetooth functionality on devices where it is not required, especially in sensitive environments. 5) Employ network segmentation to isolate vulnerable devices and reduce lateral movement opportunities. 6) Conduct regular vulnerability assessments and penetration testing focusing on Bluetooth interfaces and drivers. 7) Educate users about the risks of local exploitation and enforce policies to prevent installation of untrusted software that could trigger the vulnerability. 8) Use runtime protections such as heap integrity checks and exploit mitigation technologies (e.g., ASLR, DEP) where supported by the platform.

Description

In Bluetooth driver, there is a possible out of bounds write due to an incorrect bounds check. This could lead to local escalation of privilege with User execution privileges needed. User interaction is not needed for exploitation. Patch ID: WCNCR00412257; Issue ID: MSV-3292.

References

Community reviews

Loading reviews…