CVE-2025-20797: CWE-121 Stack Overflow in MediaTek, Inc. MT2718, MT6765, MT6768, MT6781, MT6833, MT6835, MT6853, MT6855, MT6877, MT6879, MT6893, MT6985, MT6989, MT6991, MT8186, MT8188, MT8196, MT8367, MT8391, MT8676, MT8678, MT8696, MT8766, MT8768, MT8781, MT8786, MT8788E, MT8791T, MT8792, MT8793, MT8796, MT8873, MT8883, MT8893
CVE-2025-20797 is a high-severity stack overflow vulnerability in MediaTek chipsets used in various Android versions (14. 0, 15. 0, 16. 0). It arises from a missing bounds check in the battery component, allowing out-of-bounds writes. Exploitation requires the attacker to already have System-level privileges but does not require user interaction. Successful exploitation can lead to local privilege escalation, compromising confidentiality, integrity, and availability of affected devices. The vulnerability affects a wide range of MediaTek SoCs prevalent in many Android smartphones. No known exploits are currently in the wild, but the vulnerability poses significant risk if weaponized. European organizations relying on devices with these chipsets, especially in critical infrastructure or enterprise environments, could face targeted attacks.
AI Analysis
Technical Summary
CVE-2025-20797 is a stack overflow vulnerability classified under CWE-121, discovered in the battery management component of numerous MediaTek System on Chips (SoCs), including MT2718, MT6765, MT6768, MT6781, MT6833, MT6835, MT6853, MT6855, MT6877, MT6879, MT6893, MT6985, MT6989, MT6991, MT8186, MT8188, MT8196, MT8367, MT8391, MT8676, MT8678, MT8696, MT8766, MT8768, MT8781, MT8786, MT8788E, MT8791T, MT8792, MT8793, MT8796, MT8873, MT8883, and MT8893. These chipsets are integrated into many Android devices running versions 14.0, 15.0, and 16.0. The vulnerability stems from a missing bounds check in the battery subsystem, which allows an out-of-bounds write on the stack. This flaw can be exploited locally by an attacker who already possesses System-level privileges, enabling them to escalate privileges further, potentially gaining higher control over the device. The attack does not require user interaction, increasing its risk in environments where local access is possible. The CVSS v3.1 score is 7.8 (high), reflecting the significant impact on confidentiality, integrity, and availability, combined with relatively low attack complexity and no user interaction needed. Although no known exploits are currently reported in the wild, the vulnerability represents a critical risk for devices using these MediaTek chipsets. The issue was reserved in November 2024 and published in January 2026, with patches referenced by MediaTek under internal IDs (ALPS10315812, MSV-5534). The vulnerability's exploitation could allow attackers to execute arbitrary code or disrupt device operations, severely impacting device security.
Potential Impact
For European organizations, the impact of CVE-2025-20797 is significant, especially for enterprises and critical infrastructure relying on Android devices powered by affected MediaTek chipsets. Successful exploitation could lead to local privilege escalation, enabling attackers to bypass security controls, access sensitive data, or disrupt device functionality. This could compromise confidentiality of corporate communications, integrity of device operations, and availability of mobile services. Organizations with bring-your-own-device (BYOD) policies or mobile workforce using vulnerable devices face increased risk of lateral movement or targeted attacks. The vulnerability's local nature means attackers need initial system-level access, which could be obtained via other vulnerabilities or insider threats, making it a potent escalation vector. The broad range of affected chipsets means many consumer and enterprise devices are at risk, potentially impacting sectors such as finance, healthcare, and government services across Europe. The absence of known exploits currently provides a window for proactive mitigation before widespread exploitation occurs.
Mitigation Recommendations
To mitigate CVE-2025-20797, European organizations should prioritize the following actions: 1) Identify and inventory all Android devices using affected MediaTek chipsets and running Android versions 14.0, 15.0, or 16.0. 2) Apply official patches from device manufacturers or MediaTek as soon as they become available, ensuring firmware and OS updates include the fix for this vulnerability. 3) Restrict local system-level access to trusted personnel and enforce strict access controls to minimize the risk of initial compromise. 4) Employ mobile device management (MDM) solutions to enforce security policies, monitor device integrity, and detect anomalous behavior indicative of privilege escalation attempts. 5) Educate users and administrators about the risks of local privilege escalation and the importance of timely updates. 6) Implement layered security controls such as application sandboxing and runtime protections to limit the impact of potential exploits. 7) Monitor security advisories from MediaTek and Android OEMs for updates or emerging exploit reports. 8) Consider network segmentation and endpoint detection and response (EDR) tools to detect and contain lateral movement stemming from compromised devices. These measures go beyond generic patching by emphasizing device inventory, access control, and active monitoring tailored to the vulnerability's characteristics.
Affected Countries
Germany, France, United Kingdom, Italy, Spain, Netherlands, Poland, Sweden, Belgium, Austria
CVE-2025-20797: CWE-121 Stack Overflow in MediaTek, Inc. MT2718, MT6765, MT6768, MT6781, MT6833, MT6835, MT6853, MT6855, MT6877, MT6879, MT6893, MT6985, MT6989, MT6991, MT8186, MT8188, MT8196, MT8367, MT8391, MT8676, MT8678, MT8696, MT8766, MT8768, MT8781, MT8786, MT8788E, MT8791T, MT8792, MT8793, MT8796, MT8873, MT8883, MT8893
Description
CVE-2025-20797 is a high-severity stack overflow vulnerability in MediaTek chipsets used in various Android versions (14. 0, 15. 0, 16. 0). It arises from a missing bounds check in the battery component, allowing out-of-bounds writes. Exploitation requires the attacker to already have System-level privileges but does not require user interaction. Successful exploitation can lead to local privilege escalation, compromising confidentiality, integrity, and availability of affected devices. The vulnerability affects a wide range of MediaTek SoCs prevalent in many Android smartphones. No known exploits are currently in the wild, but the vulnerability poses significant risk if weaponized. European organizations relying on devices with these chipsets, especially in critical infrastructure or enterprise environments, could face targeted attacks.
AI-Powered Analysis
Technical Analysis
CVE-2025-20797 is a stack overflow vulnerability classified under CWE-121, discovered in the battery management component of numerous MediaTek System on Chips (SoCs), including MT2718, MT6765, MT6768, MT6781, MT6833, MT6835, MT6853, MT6855, MT6877, MT6879, MT6893, MT6985, MT6989, MT6991, MT8186, MT8188, MT8196, MT8367, MT8391, MT8676, MT8678, MT8696, MT8766, MT8768, MT8781, MT8786, MT8788E, MT8791T, MT8792, MT8793, MT8796, MT8873, MT8883, and MT8893. These chipsets are integrated into many Android devices running versions 14.0, 15.0, and 16.0. The vulnerability stems from a missing bounds check in the battery subsystem, which allows an out-of-bounds write on the stack. This flaw can be exploited locally by an attacker who already possesses System-level privileges, enabling them to escalate privileges further, potentially gaining higher control over the device. The attack does not require user interaction, increasing its risk in environments where local access is possible. The CVSS v3.1 score is 7.8 (high), reflecting the significant impact on confidentiality, integrity, and availability, combined with relatively low attack complexity and no user interaction needed. Although no known exploits are currently reported in the wild, the vulnerability represents a critical risk for devices using these MediaTek chipsets. The issue was reserved in November 2024 and published in January 2026, with patches referenced by MediaTek under internal IDs (ALPS10315812, MSV-5534). The vulnerability's exploitation could allow attackers to execute arbitrary code or disrupt device operations, severely impacting device security.
Potential Impact
For European organizations, the impact of CVE-2025-20797 is significant, especially for enterprises and critical infrastructure relying on Android devices powered by affected MediaTek chipsets. Successful exploitation could lead to local privilege escalation, enabling attackers to bypass security controls, access sensitive data, or disrupt device functionality. This could compromise confidentiality of corporate communications, integrity of device operations, and availability of mobile services. Organizations with bring-your-own-device (BYOD) policies or mobile workforce using vulnerable devices face increased risk of lateral movement or targeted attacks. The vulnerability's local nature means attackers need initial system-level access, which could be obtained via other vulnerabilities or insider threats, making it a potent escalation vector. The broad range of affected chipsets means many consumer and enterprise devices are at risk, potentially impacting sectors such as finance, healthcare, and government services across Europe. The absence of known exploits currently provides a window for proactive mitigation before widespread exploitation occurs.
Mitigation Recommendations
To mitigate CVE-2025-20797, European organizations should prioritize the following actions: 1) Identify and inventory all Android devices using affected MediaTek chipsets and running Android versions 14.0, 15.0, or 16.0. 2) Apply official patches from device manufacturers or MediaTek as soon as they become available, ensuring firmware and OS updates include the fix for this vulnerability. 3) Restrict local system-level access to trusted personnel and enforce strict access controls to minimize the risk of initial compromise. 4) Employ mobile device management (MDM) solutions to enforce security policies, monitor device integrity, and detect anomalous behavior indicative of privilege escalation attempts. 5) Educate users and administrators about the risks of local privilege escalation and the importance of timely updates. 6) Implement layered security controls such as application sandboxing and runtime protections to limit the impact of potential exploits. 7) Monitor security advisories from MediaTek and Android OEMs for updates or emerging exploit reports. 8) Consider network segmentation and endpoint detection and response (EDR) tools to detect and contain lateral movement stemming from compromised devices. These measures go beyond generic patching by emphasizing device inventory, access control, and active monitoring tailored to the vulnerability's characteristics.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- MediaTek
- Date Reserved
- 2024-11-01T01:21:50.403Z
- Cvss Version
- null
- State
- PUBLISHED
Threat ID: 695c6e7a3839e44175bdd3e2
Added to database: 1/6/2026, 2:07:54 AM
Last enriched: 1/14/2026, 1:53:21 AM
Last updated: 2/7/2026, 9:14:50 AM
Views: 33
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Related Threats
CVE-2026-2079: Improper Authorization in yeqifu warehouse
MediumCVE-2026-1675: CWE-1188 Initialization of a Resource with an Insecure Default in brstefanovic Advanced Country Blocker
MediumCVE-2026-1643: CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in ariagle MP-Ukagaka
MediumCVE-2026-1634: CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in alexdtn Subitem AL Slider
MediumCVE-2026-1613: CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in mrlister1 Wonka Slide
MediumActions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.