CVE-2023-3456
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 · uneditedVulnerability of kernel raw address leakage in the hang detector module. Successful exploitation of this vulnerability may affect service confidentiality.
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 confidenceA kernel-level information disclosure vulnerability exists in the hang detector module where raw kernel memory addresses are leaked. This address leakage could potentially aid attackers in bypassing address space layout randomization (ASLR) or conducting further privilege escalation attacks by revealing kernel memory layout information.
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= 13.0.0= 2.0= 2.0.1= 2.1= 3.0.0= 3.1.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
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
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.
-
Check your HarmonyOS versionGo to Settings > About Phone > Version on the device and note the exact version number displayedAffected if The version is 2.0, 2.0.1, 2.1, 3.0.0, or 3.1.0
-
Check your EMUI versionGo to Settings > About Phone on the Huawei device and locate the EMUI version fieldAffected if The version is 12.0.0 or 13.0.0
-
Identify the kernel hang detector moduleCheck the kernel configuration or loaded modules for the presence of a hang detector component (commonly found in kernel logs or /proc filesystem on Android-based devices)Affected if The hang detector module is present and active on the device
-
Examine kernel logs for address leakageUse 'adb logcat' or access kernel message buffers (dmesg) and search for hexadecimal memory addresses that appear in hang detector related messagesAffected if Raw kernel pointers or memory addresses are visible in hang detector or watchdog related log entries
A user is affected if their HarmonyOS version is 2.0, 2.0.1, 2.1, 3.0.0, or 3.1.0, or their EMUI version is 12.0.0 or 13.0.0, and the hang detector module is active with leaked kernel addresses visible in logs.
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-supplied kernel patches for the hang detector module that address the raw address leakage issue.
- Consultation2.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,096.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-3456 — 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-2023-3456 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