CVE-2022-20012
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 mdp driver, there is a possible memory corruption due to an integer overflow. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation. Patch ID: ALPS05836478; Issue ID: ALPS05836478.
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 memory corruption vulnerability exists in the MDP (Media Display Processor) driver due to an integer overflow. This flaw allows a local attacker to escalate privileges to higher levels without requiring additional execution privileges or user interaction.
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= 10.0= 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
- 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 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 The version is exactly 10.0, 11.0, or 12.0
-
Confirm device uses MediaTek chipsetRun 'getprop ro.hardware' or 'getprop ro.mtk_platform' via ADB shell, or check chipset info in Settings > About PhoneAffected if The device contains MediaTek hardware (MDP is a MediaTek Media Display Processor component)
-
Check kernel for MDP driver presenceRun 'ls /sys/class/mdp*' or 'find /sys -name '*mdp*' 2>/dev/null' via ADB shell to locate MDP driver nodesAffected if MDP driver nodes exist on the device (indicating the vulnerable component is present)
-
Verify security patch levelRun 'getprop ro.build.version.security_patch' via ADB shell to check the installed security patch dateAffected if The security patch level is earlier than the date when ALPS05836478 was released (patched date varies by region/carrier)
A device is affected if it runs Android 10.0, 11.0, or 12.0 on MediaTek hardware with the MDP driver present and has a security patch level predating the vendor fix.
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 (ALPS05836478) or update to the latest Android security patch level that includes this fix. Until patched, limit device access to trusted users only.
Android security patch level containing ALPS05836478 (MediaTek MDP driver fix)
- Check your Android device for the availability of the latest Android security patch level from your device manufacturer
- Apply the Android security update that includes the fix for MediaTek component - this is typically included in the monthly Android Security Bulletin
- Verify the patch ALPS05836478 is included in the applied update
- If your device is no longer supported by the manufacturer, consider upgrading to a device that receives regular security updates
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,720.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-20012 — 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-20012 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