CVE-2022-38986
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 · uneditedThe HIPP module has a vulnerability of bypassing the check of the data transferred in the kernel space.Successful exploitation of this vulnerability may cause out-of-bounds access to the HIPP module and page table tampering, affecting device confidentiality and availability.
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 confidenceThe HIPP module (likely Hardware-Independent Page Table) contains a vulnerability that allows bypassing security checks on data transferred in kernel space. This enables an attacker to achieve out-of-bounds memory access within the HIPP module and manipulate page table structures, potentially leading to privilege escalation, confidentiality breaches, and availability disruption.
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= 12.0.0= 2.0CVSS 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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 Huawei EMUI versionCheck system settings under 'Settings > About Phone > Version' or run 'getprop ro.build.emui_ver' via ADB shellAffected if Version equals 12.0.0 exactly
-
Identify the Huawei HarmonyOS versionCheck system settings under 'Settings > About Phone > HarmonyOS version' or run 'getprop ro.build.version.harmonyos' via ADB shellAffected if Version equals 2.0 exactly
-
Determine if HIPP module is presentCheck for HIPP-related kernel modules or configuration files. Look for 'hipp' in /proc/modules, /system/lib/modules, or kernel cmdline parameters via 'cat /proc/cmdline'Affected if HIPP module is loaded or present on the system
-
Verify kernel build configurationInspect kernel config for HIPP-related options - check /proc/config.gz or kernel configuration files for CONFIG_HIPP or similar optionsAffected if HIPP support is enabled in the kernel configuration
The system is affected if it runs Huawei EMUI 12.0.0 or HarmonyOS 2.0 with the HIPP module present and enabled.
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 vendor-provided kernel patches addressing the HIPP module data validation bypass. If no patch available, consider disabling the HIPP module if functionality permits or implement compensating controls such as kernel runtime security monitoring.
- Consultation6.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,136.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-38986 — 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-2022-38986 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