dbcve.org
AndroidOperating system · Google

CVE-2022-20584

HIGH · 7.8 CVSS v3.1 Published 2022-12-16
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 page_number of shared_mem.c, there is a possible code execution in secure world due to improper input validation. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android kernelAndroid ID: A-238366009References: 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 · moderate confidence

In the Android kernel's shared_mem.c module, improper input validation on the page_number parameter allows a local attacker to achieve code execution in the secure world (TrustZone/TEE), resulting in local privilege escalation without requiring additional privileges or user interaction.

MitigationApply the Android security patch that addresses this vulnerability. This is a kernel-level issue requiring a vendor-supplied patch; there are no user-facing workarounds.

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:all versions

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. Check Android kernel version
    Run 'cat /proc/version' or check 'Settings > About Phone > Kernel Version' to identify your kernel version
    Affected if Any Android kernel version is potentially affected since all versions are in scope
  2. Identify shared_mem kernel module or driver
    Search for 'shared_mem' in /proc/kallsyms, /sys/module/, or check kernel config for CONFIG_SHARED_MEM or similar options using 'zcat /proc/config.gz' if available
    Affected if The shared_mem component exists in most Android kernels and is used for TrustZone shared memory operations
  3. Confirm TrustZone/TEE is present
    Check for TEE driver presence by looking in /dev/tee*, /sys/class/misc/tee*, or run 'getprop ro.hardware.trustzone' or check 'dmesg | grep -i tee'
    Affected if Most Android devices have TrustZone/TEE enabled, which is required for this vulnerability to be exploitable
  4. Verify the vulnerable page_number input validation exists
    Examine the running kernel or source for shared_mem.c - check if the page_number parameter in the shared memory ioctl/call is validated against bounds before use
    Affected if The vulnerable input validation pattern is present in the shared_mem implementation

A device is affected if it runs any version of Android with the shared_mem kernel component and has TrustZone/TEE enabled, which applies to nearly all Android devices.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the Android security patch that addresses this vulnerability. This is a kernel-level issue requiring a vendor-supplied patch; there are no user-facing workarounds.

Recommended fix Moderate confidence

November 2022 Android Security Patch Level or later (Android devices running kernel with CVE-2022-20584 fix)

  1. Ensure your Android device is updated to the November 2022 security patch level (SPL) or later. Go to Settings > Security > Security update and verify the installed version.
  2. If your device manufacturer has released an update containing the November 2022 Android security bulletin patches, install that update.
  3. After updating, verify the Android security patch level reflects November 2022 or later in Settings > About Phone > Android version or Settings > Security > Security update.
Caveat Updating to the latest security patch may require device support from your OEM; older devices may not receive this specific patch

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Android Scoped from the published advisory
  • Consultation6.0 h
  • Implementation8.0 h
  • Testing16.0 h
  • Review / QA8.0 h
38.0 hours of engineering $6,480
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-20584 — 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-20584 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