CVE-2025-20765: CWE-362 Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition') in MediaTek, Inc. MT2718, MT2737, MT6739, MT6761, MT6765, MT6768, MT6781, MT6789, MT6833, MT6835, MT6853, MT6855, MT6877, MT6878, MT6879, MT6880, MT6883, MT6885, MT6886, MT6889, MT6890, MT6893, MT6895, MT6897, MT6899, MT6980D, MT6983, MT6985, MT6989, MT6990, MT6991, MT8113, MT8115, MT8139, MT8163, MT8168, MT8169, MT8183, MT8186, MT8188, MT8512, MT8516, MT8518, MT8519, MT8532, MT8676, MT8678, MT8695, MT8696, MT8698
In aee daemon, there is a possible system crash due to a race condition. This could lead to local denial of service if a malicious actor has already obtained the System privilege. User interaction is not needed for exploitation. Patch ID: ALPS10190802; Issue ID: MSV-4833.
AI Analysis
Technical Summary
CVE-2025-20765 is a race condition vulnerability classified under CWE-362, affecting a wide range of MediaTek chipsets including MT2718 through MT8698 series. The vulnerability exists in the aee daemon, a system-level process responsible for error handling and logging on devices using these chipsets. Due to improper synchronization when accessing shared resources concurrently, a race condition can occur, leading to a system crash. This crash results in a local denial of service (DoS) condition. Exploitation requires the attacker to have already obtained System-level privileges on the device, but no user interaction is needed, making automated exploitation feasible once privileges are gained. The affected platforms include Android versions 14.0, 15.0, and 16.0, as well as openWRT 21.02 and 23.05, and Yocto 4.0, indicating a broad impact across embedded and mobile devices. The CVSS v3.1 base score is 4.7 (medium severity), reflecting the limited attack vector (local), high attack complexity, and requirement for low privileges but no confidentiality or integrity impact, only availability. No public exploits are known at this time, and no patch links were provided, but MediaTek has assigned a patch ID (ALPS10190802) and issue ID (MSV-4833) indicating remediation efforts are underway. The vulnerability could be leveraged by malicious actors who have already compromised the device to cause instability or denial of service, potentially disrupting operations or requiring device reboots.
Potential Impact
For European organizations, the impact primarily concerns availability disruption on devices using affected MediaTek chipsets. This includes smartphones, IoT devices, embedded systems, and network equipment running Android, openWRT, or Yocto with these chipsets. A successful exploit could cause system crashes leading to denial of service, which may interrupt critical communications, data collection, or operational technology processes. Although exploitation requires prior system-level access, attackers who have gained such privileges could leverage this vulnerability to maintain persistence by causing instability or forcing device reboots. This could affect sectors relying on embedded devices such as telecommunications, manufacturing, smart city infrastructure, and critical communications. The lack of confidentiality or integrity impact limits data breach risks, but availability interruptions can still cause operational and reputational damage. Additionally, the broad range of affected chipsets means many device manufacturers and vendors across Europe could be impacted, increasing the attack surface.
Mitigation Recommendations
European organizations should first identify devices using the affected MediaTek chipsets and running impacted OS versions (Android 14-16, openWRT 21.02/23.05, Yocto 4.0). Coordinate with device vendors and manufacturers to obtain and apply patches as soon as they become available, referencing MediaTek patch ID ALPS10190802. Until patches are deployed, restrict access to devices to trusted users only, minimizing the risk of privilege escalation to System level. Implement strict privilege management and monitoring to detect any unauthorized elevation of privileges. Employ runtime protection and anomaly detection to identify abnormal daemon crashes or system instability that could indicate exploitation attempts. For embedded and IoT devices, ensure secure boot and firmware integrity checks to prevent unauthorized modifications. Network segmentation can limit the spread of attacks if devices become unstable. Finally, maintain up-to-date inventories of affected hardware and software to prioritize remediation efforts effectively.
Affected Countries
Germany, France, United Kingdom, Italy, Spain, Netherlands, Poland, Sweden, Belgium, Finland
CVE-2025-20765: CWE-362 Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition') in MediaTek, Inc. MT2718, MT2737, MT6739, MT6761, MT6765, MT6768, MT6781, MT6789, MT6833, MT6835, MT6853, MT6855, MT6877, MT6878, MT6879, MT6880, MT6883, MT6885, MT6886, MT6889, MT6890, MT6893, MT6895, MT6897, MT6899, MT6980D, MT6983, MT6985, MT6989, MT6990, MT6991, MT8113, MT8115, MT8139, MT8163, MT8168, MT8169, MT8183, MT8186, MT8188, MT8512, MT8516, MT8518, MT8519, MT8532, MT8676, MT8678, MT8695, MT8696, MT8698
Description
In aee daemon, there is a possible system crash due to a race condition. This could lead to local denial of service if a malicious actor has already obtained the System privilege. User interaction is not needed for exploitation. Patch ID: ALPS10190802; Issue ID: MSV-4833.
AI-Powered Analysis
Technical Analysis
CVE-2025-20765 is a race condition vulnerability classified under CWE-362, affecting a wide range of MediaTek chipsets including MT2718 through MT8698 series. The vulnerability exists in the aee daemon, a system-level process responsible for error handling and logging on devices using these chipsets. Due to improper synchronization when accessing shared resources concurrently, a race condition can occur, leading to a system crash. This crash results in a local denial of service (DoS) condition. Exploitation requires the attacker to have already obtained System-level privileges on the device, but no user interaction is needed, making automated exploitation feasible once privileges are gained. The affected platforms include Android versions 14.0, 15.0, and 16.0, as well as openWRT 21.02 and 23.05, and Yocto 4.0, indicating a broad impact across embedded and mobile devices. The CVSS v3.1 base score is 4.7 (medium severity), reflecting the limited attack vector (local), high attack complexity, and requirement for low privileges but no confidentiality or integrity impact, only availability. No public exploits are known at this time, and no patch links were provided, but MediaTek has assigned a patch ID (ALPS10190802) and issue ID (MSV-4833) indicating remediation efforts are underway. The vulnerability could be leveraged by malicious actors who have already compromised the device to cause instability or denial of service, potentially disrupting operations or requiring device reboots.
Potential Impact
For European organizations, the impact primarily concerns availability disruption on devices using affected MediaTek chipsets. This includes smartphones, IoT devices, embedded systems, and network equipment running Android, openWRT, or Yocto with these chipsets. A successful exploit could cause system crashes leading to denial of service, which may interrupt critical communications, data collection, or operational technology processes. Although exploitation requires prior system-level access, attackers who have gained such privileges could leverage this vulnerability to maintain persistence by causing instability or forcing device reboots. This could affect sectors relying on embedded devices such as telecommunications, manufacturing, smart city infrastructure, and critical communications. The lack of confidentiality or integrity impact limits data breach risks, but availability interruptions can still cause operational and reputational damage. Additionally, the broad range of affected chipsets means many device manufacturers and vendors across Europe could be impacted, increasing the attack surface.
Mitigation Recommendations
European organizations should first identify devices using the affected MediaTek chipsets and running impacted OS versions (Android 14-16, openWRT 21.02/23.05, Yocto 4.0). Coordinate with device vendors and manufacturers to obtain and apply patches as soon as they become available, referencing MediaTek patch ID ALPS10190802. Until patches are deployed, restrict access to devices to trusted users only, minimizing the risk of privilege escalation to System level. Implement strict privilege management and monitoring to detect any unauthorized elevation of privileges. Employ runtime protection and anomaly detection to identify abnormal daemon crashes or system instability that could indicate exploitation attempts. For embedded and IoT devices, ensure secure boot and firmware integrity checks to prevent unauthorized modifications. Network segmentation can limit the spread of attacks if devices become unstable. Finally, maintain up-to-date inventories of affected hardware and software to prioritize remediation efforts effectively.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- MediaTek
- Date Reserved
- 2024-11-01T01:21:50.398Z
- Cvss Version
- null
- State
- PUBLISHED
Threat ID: 692e57b1f2f793a7de7f5f6f
Added to database: 12/2/2025, 3:06:25 AM
Last enriched: 1/12/2026, 8:59:13 PM
Last updated: 1/19/2026, 10:33:50 AM
Views: 31
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-1149: Command Injection in Totolink LR350
MediumCVE-2026-1148: Cross-Site Request Forgery in SourceCodester Patients Waiting Area Queue Management System
MediumCVE-2026-1147: Cross Site Scripting in SourceCodester Patients Waiting Area Queue Management System
Medium19th January – Threat Intelligence Report
MediumCVE-2026-1146: Cross Site Scripting in SourceCodester Patients Waiting Area Queue Management System
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.