Local availability loss via thermal-management race
Published Jan 14, 2026 · Updated Jan 14, 2026
Race condition in Huawei HarmonyOS 5.0.1, 5.1.0, and 6.0.0 allows local users to disrupt thermal-management availability. The thermal management module performs concurrent operations without proper synchronization, but Huawei has not identified the shared state or code path. Exploitation requires local execution without prior privileges; the vendor reports an availability impact but does not specify whether the device hangs, crashes, or reboots.
Summary
What happened
Race condition in Huawei HarmonyOS 5.0.1, 5.1.0, and 6.0.0 allows local users to disrupt thermal-management availability. The thermal management module performs concurrent operations without proper synchronization, but Huawei has not identified the shared state or code path. Exploitation requires local execution without prior privileges; the vendor reports an availability impact but does not specify whether the device hangs, crashes, or reboots.
The record
- CVE
- CVE-2025-68969
- Published
- Jan 14, 2026
- Updated
- Jan 14, 2026
- Vendor
- MindSpore
- Product
- HarmonyOS
- Classifications
- CWE-362, T1642
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 14, 2026CVE publishedPublication date reported by the CVE source.
- Jan 14, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=5.0.1
- Affected versionversion=5.1.0
- Affected versionversion=6.0.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo