CVE-2025-27534
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedin OpenHarmony v5.0.2 and prior versions allow a local attacker case DOS through missing release of memory.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThis is a memory leak vulnerability in OpenHarmony v5.0.2 and prior versions where a local attacker can cause Denial of Service by triggering code paths that fail to release allocated memory, leading to resource exhaustion.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 5.0.2CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify OpenHarmony installationCheck if OpenHarmony is present on the system by looking for system information files, package manifests, or version files typically found in /system/ or /etc/ directories, or use command 'getprop ro.build.version.sdk' on Android-based OpenHarmony devicesAffected if OpenHarmony is installed and the version cannot be determined or is <= 5.0.2
-
Determine exact OpenHarmony versionRun 'getprop ro.build.version.release' or check /system/etc/param/hi项参数文件 or the ohos.release file in the system partition to confirm the installed version numberAffected if The installed version is 5.0.2 or any earlier version (e.g., 5.0.1, 5.0.0, 4.x releases)
-
Verify if affected code paths are in useReview system logs and running processes for applications or services that exercise memory allocation code paths, particularly in components that handle local user-triggered operations - look for repeated allocation without corresponding deallocation patternsAffected if Applications or services that trigger the vulnerable code paths are actively running and showing symptoms of memory growth
-
Monitor for memory exhaustion symptomsUse system monitoring tools like 'dumpsys meminfo' or check /proc/meminfo over time to observe if a specific process or the system is exhibiting steadily increasing memory usage without releaseAffected if Memory usage continuously increases for processes related to OpenHarmony services without returning to baseline levels
The environment is affected if OpenHarmony version 5.0.2 or lower is installed and processes are experiencing unexplained memory growth from the vulnerable code paths.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataThe fix requires locating the code path with missing memory release and adding proper memory deallocation (e.g., free() or equivalent cleanup) at the appropriate exit points.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-27534 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-27534 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data