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-64313: CWE-362 Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition') in Huawei HarmonyOS

0
Medium
VulnerabilityCVE-2025-64313cvecve-2025-64313cwe-362
Published: Fri Nov 28 2025 (11/28/2025, 02:49:02 UTC)
Source: CVE Database V5
Vendor/Project: Huawei
Product: HarmonyOS

Description

CVE-2025-64313 is a medium-severity denial of service (DoS) vulnerability in Huawei HarmonyOS affecting versions 5. 0. 1, 5. 1. 0, and 6. 0. 0. It arises from a race condition (CWE-362) in the office service component due to improper synchronization of shared resources. Exploitation requires local access with low privileges and some user interaction, potentially causing service unavailability. No known public exploits exist yet.

AI-Powered Analysis

AILast updated: 12/05/2025, 04:33:38 UTC

Technical Analysis

CVE-2025-64313 is a vulnerability identified in Huawei's HarmonyOS, specifically within the office service component. The root cause is a race condition (CWE-362), which occurs when concurrent execution threads improperly synchronize access to shared resources. This improper synchronization can lead to inconsistent states or resource conflicts, ultimately causing a denial of service (DoS) condition. The affected versions include HarmonyOS 5.0.1, 5.1.0, and 6.0.0. The vulnerability requires local access (AV:L) with low attack complexity (AC:L), no privileges (PR:N), and some user interaction (UI:R). The scope is unchanged (S:U), and the impact affects confidentiality, integrity, and availability to a limited extent (C:L/I:L/A:L). Successful exploitation results in service unavailability, impacting system availability but not directly compromising data confidentiality or integrity. No public exploits are currently known, and no patches have been linked yet. The vulnerability was reserved on 2025-10-30 and published on 2025-11-28. The race condition likely arises during concurrent operations within the office service, which could be triggered by multiple processes or threads accessing shared resources without proper locking or synchronization mechanisms. This can cause the service to crash or become unresponsive, leading to denial of service conditions. Given the nature of the vulnerability, exploitation would require an attacker to have local access to the device and to perform specific user interactions to trigger the race condition. This limits the attack vector primarily to insiders or malware already running on the device. The vulnerability's medium severity reflects the balance between its impact and the difficulty of exploitation.

Potential Impact

For European organizations, the primary impact of CVE-2025-64313 is the potential denial of service of office services on devices running affected versions of Huawei HarmonyOS. This can disrupt business operations, particularly in environments where HarmonyOS devices are integrated into workflows or critical communication systems. The availability impact could lead to productivity loss, delayed communications, and potential cascading effects if the office service is part of larger automated processes. Confidentiality and integrity impacts are limited, reducing the risk of data breaches or unauthorized data modification. However, the disruption of services can affect operational continuity and user trust. Organizations relying on Huawei devices for office-related tasks should be aware of this risk, especially in sectors such as government, telecommunications, and enterprises with significant Huawei device deployments. The requirement for local access and user interaction reduces the likelihood of remote exploitation but does not eliminate insider threats or malware-based attacks. The absence of known exploits in the wild currently lowers immediate risk but emphasizes the importance of proactive mitigation.

Mitigation Recommendations

1. Monitor Huawei’s official security advisories closely for patches addressing CVE-2025-64313 and apply them promptly once available. 2. Restrict local access to devices running affected versions of HarmonyOS by enforcing strict physical and logical access controls, including multi-factor authentication and device lockdown policies. 3. Implement endpoint protection solutions capable of detecting anomalous process behavior or race condition exploitation attempts within office services. 4. Educate users about the risks of interacting with untrusted applications or processes that could trigger the race condition, reducing inadvertent exploitation. 5. Employ application whitelisting and privilege restrictions to limit the execution of unauthorized code that might exploit the vulnerability. 6. Conduct regular audits of device configurations and installed software versions to identify and remediate vulnerable systems. 7. Where possible, isolate critical office service environments from less trusted networks or user groups to minimize exposure. 8. Develop incident response plans that include detection and recovery procedures for denial of service events related to this vulnerability. These measures go beyond generic advice by focusing on access control, user awareness, and proactive monitoring tailored to the specific nature of the race condition vulnerability in HarmonyOS office services.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
huawei
Date Reserved
2025-10-30T02:00:28.698Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 692910b5ce4290e3e3b49073

Added to database: 11/28/2025, 3:02:13 AM

Last enriched: 12/5/2025, 4:33:38 AM

Last updated: 1/19/2026, 8:38:26 PM

Views: 83

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 in Console -> Billing for AI refresh and higher limits.

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

Latest Threats