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-20722: CWE-190 Integer Overflow in MediaTek, Inc. MT6835, MT6878, MT6886, MT6897, MT6899, MT6980D, MT6985, MT6989, MT6990, MT6991, MT8676, MT8678, MT8775, MT8791T, MT8796, MT8873

0
Medium
VulnerabilityCVE-2025-20722cvecve-2025-20722cwe-190
Published: Tue Oct 14 2025 (10/14/2025, 09:11:48 UTC)
Source: CVE Database V5
Vendor/Project: MediaTek, Inc.
Product: MT6835, MT6878, MT6886, MT6897, MT6899, MT6980D, MT6985, MT6989, MT6990, MT6991, MT8676, MT8678, MT8775, MT8791T, MT8796, MT8873

Description

In gnss driver, there is a possible out of bounds read due to an integer overflow. This could lead to local information disclosure if a malicious actor has already obtained the System privilege. User interaction is not needed for exploitation. Patch ID: ALPS09920036; Issue ID: MSV-3798.

AI-Powered Analysis

AILast updated: 10/14/2025, 09:38:40 UTC

Technical Analysis

CVE-2025-20722 is a vulnerability classified under CWE-190 (Integer Overflow) affecting the GNSS (Global Navigation Satellite System) driver in a broad range of MediaTek chipsets including MT6835, MT6878, MT6886, MT6897, MT6899, MT6980D, MT6985, MT6989, MT6990, MT6991, MT8676, MT8678, MT8775, MT8791T, MT8796, and MT8873. These chipsets are embedded in devices running Android versions 14.0 and 15.0, openWRT 21.02 and 23.05, and RDKB 24Q1. The vulnerability arises from an integer overflow condition that leads to an out-of-bounds read within the GNSS driver code. This flaw can be exploited by an attacker who already has obtained system-level privileges on the device, enabling local information disclosure without requiring any user interaction. The out-of-bounds read may expose sensitive memory contents, potentially leaking confidential information. Although no public exploits are known at this time, the vulnerability poses a risk in scenarios where an attacker has escalated privileges or gained local system access through other means. The vendor has acknowledged the issue and assigned a patch ID (ALPS09920036), but no direct patch links are provided. The vulnerability does not have an assigned CVSS score yet, and the attack vector is local with no user interaction needed. The flaw impacts confidentiality primarily, with no direct integrity or availability consequences reported.

Potential Impact

For European organizations, the primary impact of CVE-2025-20722 lies in the potential for local information disclosure on devices using affected MediaTek chipsets. This could compromise sensitive data stored in memory, including cryptographic keys, credentials, or location data, which may be leveraged for further attacks or espionage. Organizations deploying Android 14/15 devices, openWRT-based routers, or RDKB-based broadband equipment with these chipsets are at risk, especially in sectors with high security requirements such as telecommunications, critical infrastructure, and government. The vulnerability requires prior system-level access, so it is less likely to be exploited remotely but could be part of a multi-stage attack chain. The lack of user interaction lowers the barrier for exploitation once system privileges are obtained. This could facilitate lateral movement or data exfiltration within corporate or governmental networks. The broad chipset coverage increases the attack surface, affecting a wide range of consumer and enterprise devices prevalent in Europe. Failure to patch could lead to data breaches, regulatory non-compliance, and reputational damage.

Mitigation Recommendations

1. Apply vendor-supplied patches immediately once available to eliminate the integer overflow condition in the GNSS driver. 2. Restrict system-level access on affected devices by enforcing strict privilege separation and minimizing the number of users or processes with elevated rights. 3. Implement robust endpoint detection and response (EDR) solutions to monitor for suspicious local activity indicative of privilege escalation or exploitation attempts. 4. Conduct regular audits of device firmware and software versions to identify and remediate unpatched vulnerable systems. 5. Employ network segmentation to isolate critical devices running affected MediaTek chipsets, limiting lateral movement opportunities. 6. For IoT and embedded devices, consider deploying runtime integrity verification and anomaly detection to detect exploitation attempts. 7. Educate system administrators and security teams about the vulnerability and the importance of timely patching and access control. 8. Collaborate with vendors and suppliers to ensure supply chain security and timely vulnerability disclosures.

Need more detailed analysis?Get Pro

Technical Details

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

Threat ID: 68ee16317eab8b438c025d4d

Added to database: 10/14/2025, 9:21:53 AM

Last enriched: 10/14/2025, 9:38:40 AM

Last updated: 10/15/2025, 10:01:25 PM

Views: 9

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 enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats