liteos_a has a race condition vulnerability

published 2025-08-11 last yr. modified 2026-06-17 4mo ago also EUVD-2025-24116

cvss: 8.4; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.1%; EPSS 0.1% chance of exploitation in 30 days, percentile 1%
public exploits: 0; none known

in OpenHarmony v5.0.3 and prior versions allow a local attacker arbitrary code execution in tcb through race condition.

Is CVE-2025-25278 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation: none
Automatable: no
Technical impact: total
Assessed: last yr. (2025-08-11)

Exploit prediction

0.12% chance of exploitation in the next 30 days, higher than 1% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
CNA	3.1	8.4	CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:H
NVD	3.1	7.0	CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H

Affected products

OpenHarmony OpenHarmony

Classification

Weakness

CWE-362 Concurrent Execution using Shared Resource with Improper Synchronization

References

gitee.com /openharmony/security/blob/master/zh/security-disclosure/2025/2025-08.md
vendor-advisory

Sources

CVE List CVE-2025-25278
NVD CVE-2025-25278

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.