dbcve.org
AndroidOperating system · Google

CVE-2022-20040

HIGH · 7.8 CVSS v3.1 Published 2022-02-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
Zero-click

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 · unedited
In power_hal_manager_service, there is a possible permission bypass due to a stack-based buffer overflow. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation. Patch ID: ALPS06219150; Issue ID: ALPS06219150.

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 confidence

A stack-based buffer overflow in the power_hal_manager_service allows a local attacker to bypass permission checks and escalate privileges. The vulnerability requires no user interaction or additional execution privileges, enabling direct local privilege escalation through the overflow.

MitigationApply vendor patch ALPS06219150, which addresses the stack-based buffer overflow in power_hal_manager_service. This is typically delivered through device firmware/system updates from the OEM.

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
AndroidOperating system
Affected:= 11.0= 12.0

CVSS 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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Android version
    Run 'getprop ro.build.version.release' or check Settings > About Phone > Android version
    Affected if The version returns exactly '11' or '12' (not 11.0.x or 12.0.x variants, but the exact versions 11.0 and 12.0) - note this CVE specifically affects = 11.0 and = 12.0 meaning those exact releases, check your full build ID with 'getprop ro.build.id' to confirm
  2. Verify power_hal_manager_service exists
    Check for the presence of power_hal_manager_service in the system. Look in /vendor/lib/hw/ or /system/lib/hw/ for files matching 'power.*.so' or search the service list with 'lshal | grep power_hal'
    Affected if The power_hal_manager_service or related power HAL implementation is present on the device
  3. Check vendor security patch level
    Run 'getprop ro.build.version.security_patch' to see the installed security patch date
    Affected if The security patch level is earlier than the date when ALPS06219150 was released by your OEM, or the patch level does not include the fix for this vulnerability
  4. Check OEM-specific patch indicator
    Query vendor-specific build properties with 'getprop | grep -i patch' or 'getprop ro.vendor.build.security_patch' to see if the vendor-specific fix (ALPS06219150) has been applied
    Affected if The vendor patch ALPS06219150 is not reflected in the build properties, indicating the fix is not present
  5. Verify SELinux context for power service
    Run 'ls -la /vendor/etc/selinux/vendor_seapp_contexts' and check if power_hal_manager_service has proper SELinux enforcement, or run 'ps -AZ | grep power_hal' to check the service process context
    Affected if The service runs with elevated privileges or overly permissive SELinux context that could be exploited via this buffer overflow

A device is affected if it runs Android version 11.0 or 12.0 exactly, contains the power_hal_manager_service component, and lacks the vendor patch ALPS06219150 in the security patch level.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor patch ALPS06219150, which addresses the stack-based buffer overflow in power_hal_manager_service. This is typically delivered through device firmware/system updates from the OEM.

Fix this in Android Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,380
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,808.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-20040 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-20040 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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