CVE-2022-20183
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 · uneditedIn hypx_create_blob_dmabuf of faceauth_hypx.c, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of privilege with System execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android kernelAndroid ID: A-188911154References: N/A
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 · high confidenceA missing bounds check in the hypx_create_blob_dmabuf function of faceauth_hypx.c in the Android kernel allows an out-of-bounds write. This occurs when processing blob data in the face authentication subsystem, where insufficient validation of input size before memory operations permits writing beyond allocated buffers. An attacker with System execution privileges can exploit this for local privilege escalation.
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 dataall versionsCVSS 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
- Local
- Complexity
- Low
- Privileges
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/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.
-
Confirm the system is AndroidCheck for Android by examining /system/build.prop or running 'uname -a' to see if the kernel identifies as AndroidAffected if The system is not Android-based, as this vulnerability only affects Android kernels
-
Determine the Android security patch levelRead the ro.build.version.security_patch property from /system/build.prop (e.g., 'cat /system/build.prop | grep security_patch') or check via 'getprop ro.build.version.security_patch'Affected if The patch level is earlier than the fix for A-188911154, as all versions prior to the patched release are affected
-
Check if the face authentication driver is presentSearch for the faceauth kernel module or driver file in /lib/modules/ or via 'lsmod | grep face' and check for /dev/video* devices related to face authAffected if The face authentication subsystem (faceauth_hypx) is loaded or available on the device, as the vulnerability lies in its hypx_create_blob_dmabuf function processing blob data
-
Identify the kernel source file existenceCheck if the vulnerable source file faceauth_hypx.c exists in the kernel or if the compiled module is present on the systemAffected if The faceauth_hypx driver binary/module is present in the system's kernel or modules directory
A user is affected if the system runs Android with a security patch level predating the fix for A-188911154 and has the face authentication subsystem (faceauth_hypx) 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 the Android security patch that includes the fix for A-188911154, which adds proper bounds validation in the hypx_create_blob_dmabuf function. The fix requires modifying the kernel driver to validate buffer sizes before performing the write operation.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-20183 — 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-20183 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