Kernel crash via frame scheduler null dereference
Published Jul 11, 2022 · Updated Aug 3, 2024
A null pointer dereference in Huawei HarmonyOS 2.0 and EMUI 11.0.1 and 12.0.0 allows remote attackers to crash the kernel. Huawei identifies the frame scheduling module but has not published the trigger or the operation that leaves the scheduler with a null pointer. Network access without authentication or user interaction is sufficient, and the documented consequence is loss of kernel availability.
Summary
What happened
A null pointer dereference in Huawei HarmonyOS 2.0 and EMUI 11.0.1 and 12.0.0 allows remote attackers to crash the kernel. Huawei identifies the frame scheduling module but has not published the trigger or the operation that leaves the scheduler with a null pointer. Network access without authentication or user interaction is sufficient, and the documented consequence is loss of kernel availability.
The record
- CVE
- CVE-2022-34736
- Published
- Jul 11, 2022
- Updated
- Aug 3, 2024
- Vendor
- Huawei Technologies Co., Ltd.
- Product
- HarmonyOS
- Classifications
- CWE-476, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 11, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 2024Record 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=2.0
What conditions does exploitation require?
What is affected?
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.
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