CVE-2025-24844
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.3 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 confidenceOpenHarmony v5.0.3 and prior versions contain a memory leak vulnerability where memory is not properly released, allowing a local attacker to cause denial of service by exhausting available memory resources.
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.3CVSS 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 the installed OpenHarmony versionRun 'hdc shell' to connect to the device, then execute 'getprop ro.build.version.sdk' or check '/system/etc/version' to retrieve the OpenHarmony version numberAffected if The displayed version is 5.0.3 or any earlier version (e.g., 5.0.2, 5.0.1, 4.x) indicating the device runs a vulnerable release
-
Confirm the OpenHarmony release branchCheck the build information by running 'hdc shell cat /system/build.prop' or inspecting the OTA update package metadata if available, looking for the OpenAtom release tagAffected if The build shows 'OpenHarmony 5.0.3' or earlier in the version string, confirming an unpatched release
-
Monitor memory behavior during prolonged operationUse 'hdc shell' to run 'dumpsys meminfo' periodically over several hours or days, observing whether the RSS (Resident Set Size) or PSS (Proportional Set Size) continuously grows without stabilizingAffected if Memory usage shows steady increases without returning to baseline levels, indicating a potential memory leak consistent with this vulnerability
-
Check for available security patchesReview the device's security patch level by running 'hdc shell getprop ro.build.version.security_patch' or checking the OpenHarmony security bulletin for any post-v5.0.3 updates addressing memory managementAffected if The security patch level is blank, missing, or dated before any fix release for CVE-2025-24844, meaning the memory leak remains unmitigated
You are affected if the installed OpenHarmony version is 5.0.3 or earlier and no security patch addressing the memory leak has been applied.
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 dataApply any available security patch for OpenHarmony beyond v5.0.3. If no patch is available, conduct source code review to identify and add proper memory deallocation for the affected code path.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-24844 — 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-24844 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