CVE-2022-21787
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 audio DSP, 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. Patch ID: ALPS06558844; Issue ID: ALPS06558844.
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 confidenceA vulnerability in the audio DSP (Digital Signal Processor) allows an out-of-bounds write due to a missing bounds check. This memory corruption issue can be exploited locally to escalate privileges to System level without requiring user interaction. The flaw is in the audio processing subsystem and the patch is identified as ALPS06558844 (MediaTek/ALPS).
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= 11.0= 12.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
- 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.
-
Check Android OS versionGo to Settings > About Phone > Android version, or run 'getprop ro.build.version.release' via ADB shellAffected if Version displays as exactly 11.0 or 12.0 (these are the only affected versions per the CVE)
-
Identify chipset vendorRun 'getprop ro.chipname' or 'getprop ro.hardware' via ADB shell, or check device specificationsAffected if Device uses a MediaTek chipset, since the patch ALPS06558844 is a MediaTek/ALPS patch
-
Verify audio subsystem is activeCheck that /dev/audio_dsp or similar audio DSP device nodes exist: run 'ls -la /dev/audio*' via ADB shellAffected if Audio DSP device nodes are present and accessible (the vulnerability exists in the audio DSP)
You are affected if your device runs Android 11.0 or 12.0, uses a MediaTek chipset with the vulnerable audio DSP subsystem, and the audio processing component is enabled (which it is by default on affected Android versions).
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.
dbcve · scopedApply the vendor patch ALPS06558844 via system firmware update. As this is a system-level audio component vulnerability allowing privilege escalation, prioritize patching on affected devices.
Android Security Patch Level February 2022 or later (check with device manufacturer for specific release)
- 1. Ensure the device is running the latest Android security patch level available from the device manufacturer.
- 2. Check for system updates in Settings > System > Software Update (or Settings > About Phone > Software Update) and install any available updates.
- 3. If the manufacturer has released a specific update addressing Patch ID ALPS06558844, install that update.
- 4. For enterprise-managed devices, ensure Mobile Device Management (MDM) policies are configured to enforce regular security patch installations.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing8.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 $4,864.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-21787 — 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-21787 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