dbcve.org
AndroidOperating system · Google

CVE-2022-20464

MEDIUM · 5.5 CVSS v3.1 Published 2022-10-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
57/100
Remediation priority · Elevated
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 various functions of ap_input_processor.c, there is a possible way to record audio during a phone call due to a logic error in the code. This could lead to local information disclosure with User execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android kernelAndroid ID: A-236042696References: 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

A logic error in the Android kernel's ap_input_processor.c allows unauthorized audio recording during phone calls. The vulnerability enables a local attacker to capture audio from phone calls due to missing or incorrect authorization checks in the audio input processing functions, leading to local information disclosure.

MitigationApply the Android security patch for CVE-2022-20464, which corrects the logic error in the audio input processing code to enforce proper authorization before allowing audio recording during calls.

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
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/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 checks

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

  1. Check Android Security Patch Level
    Go to Settings > About Phone > Security Patch Level (or Android version) and note the date shown
    Affected if The Security Patch Level is earlier than September 2022, as patches for CVE-2022-20464 were released in the September 2022 Android security bulletin
  2. Verify kernel version
    Run 'cat /proc/version' or check kernel version in Settings > About Phone > Kernel Version
    Affected if The kernel version is older than the patched kernel containing the fix for ap_input_processor.c authorization logic
  3. Confirm affected component is present
    Verify the device has audio call functionality (the device must support phone calls and have audio input capability)
    Affected if The device supports phone calls with audio input - the vulnerability exploits the audio input processing during calls, so any Android device capable of making calls is potentially affected if unpatched
  4. Check for audio recording permissions during calls
    This is a kernel-level vulnerability in the audio input path; detection requires examining if audio can be recorded during an active call without proper authorization
    Affected if Audio input is processed during calls without proper authorization checks - the vulnerability exists when the kernel lacks the corrected logic in ap_input_processor.c

The device is affected if it runs an Android version with a Security Patch Level prior to the September 2022 update, as all Android versions contain the vulnerable code in the kernel's audio input processing until the patch is applied.

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 for CVE-2022-20464, which corrects the logic error in the audio input processing code to enforce proper authorization before allowing audio recording during calls.

Recommended fix Moderate confidence

December 2022 Android Security Patch Level or later

  1. 1. Check your current Android security patch level by going to Settings > About Phone > Android version or Settings > Security > Security update
  2. 2. Go to Settings > System > Software Update (or Settings > About Phone > Software Update) to check for available updates
  3. 3. Download and install the December 2022 Android Security Patch Level (SPL) or later
  4. 4. After installation, verify the security patch level has been updated in Settings > About Phone > Android version
Caveat Security updates typically have no breaking changes; ensure device is charged and backup important data before updating

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

Fix this in Android Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,720
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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