dbcve.org
OpenharmonyApplication

CVE-2022-45126

HIGH · 7.8 CVSS v3.1 Published 2023-01-09
Fix available
A fix is available. Upgrade to after 3.1.4 or later.
See remediation →
80/100
Remediation priority · High
Zero-click

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 · unedited
Kernel subsystem within OpenHarmony-v3.1.4 and prior versions in kernel_liteos_a has a kernel stack overflow vulnerability when call SysClockGettime. 4 bytes padding data from kernel stack are copied to user space incorrectly and leaked.

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 · high confidence

A kernel stack overflow/information disclosure vulnerability exists in the kernel_liteos_a subsystem of OpenHarmony v3.1.4 and prior versions. The SysClockGettime system call incorrectly copies 4 bytes of kernel stack padding data to user space, leaking potentially sensitive kernel memory contents to unprivileged users.

MitigationUpgrade to OpenHarmony v3.2.0 or later which contains the corrected kernel code. If upgrade is not feasible, apply a patch to ensure SysClockGettime only copies the intended struct fields (timespec) to user space and does not include padding bytes from the kernel stack.

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
OpenharmonyApplication
Affected:>= 3.1.0, <= 3.1.4
OpenharmonyOperating system
Affected:>= 1.1.0, <= 1.1.5>= 3.0, <= 3.0.6

CVSS 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
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed OpenHarmony version
    Check the system version file or use 'cat /proc/version' or 'uname -a' to determine the OpenHarmony version number
    Affected if The version is between 3.1.0 and 3.1.4 (Openharmony) or between 1.1.0-1.1.5 or 3.0-3.0.6 (Openatom Openharmony)
  2. Confirm kernel_liteos_a subsystem is in use
    Check kernel build configuration or system information for 'kernel_liteos_a' designation
    Affected if The system uses the kernel_liteos_a kernel subsystem
  3. Verify SysClockGettime syscall accessibility
    Check if unprivileged user processes can invoke the SysClockGettime system call by examining syscall table configuration or testing with a non-privileged process calling clock_gettime()
    Affected if The SysClockGettime syscall is accessible to unprivileged users without restrictions

A system is affected if it runs OpenHarmony version 3.1.0-3.1.4 or the specified Openatom versions and uses the kernel_liteos_a subsystem with the SysClockGettime syscall exposed to unprivileged users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 3.1.4
Interim mitigation

Upgrade to OpenHarmony v3.2.0 or later which contains the corrected kernel code. If upgrade is not feasible, apply a patch to ensure SysClockGettime only copies the intended struct fields (timespec) to user space and does not include padding bytes from the kernel stack.

Recommended fix Moderate confidence

OpenHarmony 3.1.5 (or latest stable release for each affected branch)

  1. 1. Identify the specific OpenHarmony release line in use (1.1.x, 3.0.x, or 3.1.x)
  2. 2. For 3.1.x branch: upgrade to OpenHarmony 3.1.5 or later (the description indicates v3.1.4 and prior are affected)
  3. 3. For 3.0.x branch: upgrade to a version greater than 3.0.6
  4. 4. For 1.1.x branch: upgrade to a version greater than 1.1.5
  5. 5. Verify the fix by confirming kernel_liteos_a component no longer leaks kernel stack padding in SysClockGettime syscall
  6. 6. Test the time-related syscalls functionality after upgrade
Caveat Kernel-level changes may affect syscall compatibility; test time-related functionality thoroughly

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Openharmony Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-45126 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-45126 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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