CVE-2023-46761
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 · uneditedOut-of-bounds write vulnerability in the kernel driver module. Successful exploitation of this vulnerability may cause process exceptions.
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 · low confidenceAn out-of-bounds write vulnerability exists in a kernel driver module that allows writing data beyond allocated memory boundaries. Successful exploitation can cause process exceptions, potentially leading to denial of service or potentially privilege escalation depending on the specific driver context.
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= 13.0.0= 3.0.0= 3.1.0= 4.0.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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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.
-
Check Huawei EMUI versionNavigate to Settings > About Phone > Version on the Huawei device, or run 'getprop ro.build.version.emui' via ADB shellAffected if Version equals exactly 13.0.0
-
Check Huawei HarmonyOS versionNavigate to Settings > About Phone > Version on the Huawei device, or run 'getprop ro.build.version.harmonyos' via ADB shellAffected if Version equals exactly 3.0.0, 3.1.0, or 4.0.0
-
Identify loaded kernel driver modulesRun 'lsmod' or check /proc/modules via ADB shell to list loaded kernel modules; look for any third-party or vendor-specific driver modules that may contain the vulnerable codeAffected if A kernel driver module matching the affected vendor driver is loaded and contains the out-of-bounds write vulnerability
-
Check for untrusted code execution pathsReview installed applications and running services for any that can interact directly with kernel drivers or memory-mapped I/O, particularly those from untrusted sourcesAffected if Untrusted applications have permission to interact with the vulnerable kernel driver interface
The device is affected if it runs EMUI 13.0.0 or HarmonyOS 3.0.0/3.1.0/4.0.0 with the vulnerable kernel driver module loaded and accessible to untrusted code execution contexts.
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 patches for the affected kernel driver. Until patched, limit access to untrusted code that can interact with the vulnerable driver and monitor for anomalous system behavior.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-46761 — 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-46761 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