Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-20672: CWE-122 Heap Overflow in MediaTek, Inc. MT7902, MT7921, MT7922, MT7925, MT7927

0
Critical
VulnerabilityCVE-2025-20672cvecve-2025-20672cwe-122
Published: Mon Jun 02 2025 (06/02/2025, 02:29:38 UTC)
Source: CVE Database V5
Vendor/Project: MediaTek, Inc.
Product: MT7902, MT7921, MT7922, MT7925, MT7927

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.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 02/26/2026, 20:45:58 UTC

Technical Analysis

CVE-2025-20672 is a heap overflow vulnerability categorized under CWE-122 found in the Bluetooth driver implementations of MediaTek's MT7902, MT7921, MT7922, MT7925, and MT7927 chipsets. The root cause is an incorrect bounds check that allows an attacker to perform an out-of-bounds write on the heap memory. This vulnerability can be exploited locally by an attacker with user-level execution privileges, without requiring any user interaction, to escalate privileges on the affected system. The flaw affects devices running NB SDK release 3.6 and earlier, which incorporate these chipsets. The vulnerability impacts confidentiality, integrity, and availability, as successful exploitation could allow arbitrary code execution or system compromise. The CVSS v3.1 base score is 9.8 (critical), reflecting network attack vector, low attack complexity, no privileges required, no user interaction, and full impact on confidentiality, integrity, and availability. Although no public exploits have been reported yet, the severity and ease of exploitation make this a high-risk vulnerability. MediaTek has assigned Patch ID WCNCR00412257 and Issue ID MSV-3292 for remediation, but no public patch links are currently available. The vulnerability is particularly concerning for devices relying on these chipsets for Bluetooth connectivity, including laptops, IoT devices, and mobile platforms.

Potential Impact

The impact of CVE-2025-20672 is severe for organizations worldwide using devices with affected MediaTek chipsets. Exploitation allows local attackers to escalate privileges from user-level to potentially system-level, enabling full control over the device. This can lead to unauthorized access to sensitive data, installation of persistent malware, disruption of device functionality, and lateral movement within networks. Given the Bluetooth driver context, attackers may exploit this vulnerability remotely if they can execute code locally via Bluetooth interfaces or through compromised applications. The lack of required user interaction increases the risk of automated or stealthy attacks. Organizations deploying affected devices in critical infrastructure, enterprise environments, or consumer electronics face significant risks of data breaches, operational disruption, and reputational damage. The widespread use of MediaTek chipsets in various markets amplifies the potential attack surface globally.

Mitigation Recommendations

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.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.1
Assigner Short Name
MediaTek
Date Reserved
2024-11-01T01:21:50.370Z
Cvss Version
null
State
PUBLISHED

Threat ID: 683d16f6182aa0cae230af00

Added to database: 6/2/2025, 3:13:58 AM

Last enriched: 2/26/2026, 8:45:58 PM

Last updated: 3/26/2026, 10:07:21 AM

Views: 76

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses