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-20745: CWE-416 Use After Free in MediaTek, Inc. MT2718, MT6989, MT6991, MT8370, MT8390, MT8395, MT8676, MT8678, MT87920

0
Medium
VulnerabilityCVE-2025-20745cvecve-2025-20745cwe-416
Published: Tue Nov 04 2025 (11/04/2025, 06:20:03 UTC)
Source: CVE Database V5
Vendor/Project: MediaTek, Inc.
Product: MT2718, MT6989, MT6991, MT8370, MT8390, MT8395, MT8676, MT8678, MT87920

Description

In apusys, there is a possible memory corruption due to use after free. 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: ALPS10095441; Issue ID: MSV-4294.

AI-Powered Analysis

AILast updated: 11/11/2025, 07:25:47 UTC

Technical Analysis

CVE-2025-20745 is a use-after-free vulnerability classified under CWE-416 found in the apusys subsystem of several MediaTek SoCs including MT2718, MT6989, MT6991, MT8370, MT8390, MT8395, MT8676, MT8678, and MT87920. These chipsets are integrated into devices running Android versions 13.0 through 15.0. The vulnerability arises when a memory object is freed but subsequently accessed, leading to memory corruption. This flaw can be exploited locally by an attacker who already possesses system-level privileges to escalate their privileges further, potentially gaining higher control over the device. The attack does not require user interaction, increasing the risk in environments where system privileges are already compromised. However, the initial requirement of system privilege limits the attack surface. The vulnerability affects confidentiality, integrity, and availability, but only to a limited degree given the prerequisite access. No public exploits have been reported, and MediaTek has assigned a patch ID ALPS10095441 to address the issue. The CVSS v3.1 base score is 4.2, reflecting a medium severity level due to the local attack vector and high privileges required. The vulnerability is relevant to embedded and mobile devices using these MediaTek chipsets, which are common in various consumer electronics and IoT devices.

Potential Impact

For European organizations, the primary impact is on devices incorporating the affected MediaTek chipsets running Android 13 to 15, including smartphones, tablets, and IoT devices. If an attacker gains system privileges on such devices, they could exploit this vulnerability to escalate privileges further, potentially leading to unauthorized access to sensitive data, modification of system components, or disruption of device functionality. This could compromise corporate mobile endpoints, especially in Bring Your Own Device (BYOD) scenarios or in environments where devices have elevated privileges due to misconfiguration or rooting. The vulnerability could also affect embedded systems in industrial or consumer IoT devices, potentially impacting operational technology security. While the initial requirement for system privileges limits exploitation likelihood, the vulnerability could be leveraged as part of a multi-stage attack chain. The absence of user interaction for exploitation increases risk in automated or unattended environments. Overall, the impact is moderate but significant in contexts where device integrity and confidentiality are critical.

Mitigation Recommendations

Organizations should prioritize patching affected devices as soon as MediaTek or device manufacturers release updates addressing CVE-2025-20745 (patch ID ALPS10095441). Until patches are applied, restrict access to devices to trusted users and monitor for signs of privilege escalation or unusual system behavior. Employ mobile device management (MDM) solutions to enforce security policies and control privilege levels on Android devices. Avoid rooting or granting unnecessary system privileges to applications or users to reduce the attack surface. Conduct regular security audits on devices using affected chipsets to detect potential compromises. For IoT deployments, segment networks to isolate vulnerable devices and limit lateral movement. Security teams should also monitor threat intelligence feeds for any emerging exploits targeting this vulnerability. Implementing application whitelisting and behavior monitoring on endpoints can help detect exploitation attempts. Finally, coordinate with device vendors to ensure timely firmware and OS updates.

Need more detailed analysis?Get Pro

Technical Details

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

Threat ID: 6909a1aad66f5e62e384935a

Added to database: 11/4/2025, 6:48:10 AM

Last enriched: 11/11/2025, 7:25:47 AM

Last updated: 12/18/2025, 1:47:28 AM

Views: 72

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