Kernel data disclosure via uninitialized timespec padding
Published Jan 9, 2023 · Updated Apr 9, 2025
Kernel stack data exposure in affected OpenHarmony releases allows local users to read four bytes of kernel memory via SysClockGettime. The kernel_liteos_a SysClockGettime path copies a timespec structure with four uninitialized padding bytes from the kernel stack to user space. The call is locally reachable without privileges or user interaction; no remote trigger, data modification, or broader disclosure is documented.
Summary
What happened
Kernel stack data exposure in affected OpenHarmony releases allows local users to read four bytes of kernel memory via SysClockGettime. The kernel_liteos_a SysClockGettime path copies a timespec structure with four uninitialized padding bytes from the kernel stack to user space. The call is locally reachable without privileges or user interaction; no remote trigger, data modification, or broader disclosure is documented.
The record
- CVE
- CVE-2022-45126
- Published
- Jan 9, 2023
- Updated
- Apr 9, 2025
- Vendor
- OpenHarmony
- Product
- OpenHarmony
- Classifications
- CWE-120, CWE-787, CAPEC-131, T1005
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 9, 2023CVE publishedPublication date reported by the CVE source.
- Apr 9, 2025Record 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=1.1.0 <=1.1.5
- Affected versionversion=3.0.0 <=3.0.6
- Affected versionversion=3.1.0 <=3.1.4
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