dbcve.org
AndroidOperating system · Google

CVE-2022-26427

MEDIUM · 6.7 CVSS v3.1 Published 2022-08-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/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 camera isp, 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: ALPS07085540; Issue ID: ALPS07085540.

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 · high confidence

A missing bounds check in the camera ISP (Image Signal Processor) allows an out-of-bounds write vulnerability, which can be exploited for local privilege escalation from System privileges. The vulnerability resides in the MediaTek/ALPS camera driver code (Patch ID ALPS07085540) and requires System-level access to exploit but needs no user interaction.

MitigationApply vendor patch ALPS07085540 which adds proper bounds checking to the camera ISP driver. Since this is a firmware/driver-level fix, coordinate with the device OEM or MediaTek for the appropriate system update.

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
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 checks

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

  1. Identify the chipset vendor
    Run 'getprop ro.hardware' or check /proc/cpuinfo to determine if the device uses a MediaTek chipset. This vulnerability resides in MediaTek's ALPS camera driver.
    Affected if The device does not use a MediaTek chipset - this flaw is specific to MediaTek hardware.
  2. Check Android OS version
    Run 'getprop ro.build.version.release' to obtain the installed Android version.
    Affected if The Android version is exactly 11.0 or 12.0 - these are the only affected versions listed.
  3. Verify MediaTek camera ISP driver presence
    Check for the presence of camera ISP driver modules by examining /proc/modules or using 'lsmod' to list loaded kernel modules related to camera ISP.
    Affected if The camera ISP driver module is loaded and the device meets the chipset and version criteria above.
  4. Confirm driver version against patch level
    Obtain the camera driver version through vendor-specific diagnostic tools or check system logs for MediaTek camera driver load messages referencing ALPS07085540.
    Affected if The camera driver version predates the ALPS07085540 patch - the vulnerability exists when bounds checking is missing in the ISP driver.

The device is affected if it runs Android 11.0 or 12.0 on a MediaTek chipset with the vulnerable camera ISP driver present (unpatched ALPS07085540).

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 vendor patch ALPS07085540 which adds proper bounds checking to the camera ISP driver. Since this is a firmware/driver-level fix, coordinate with the device OEM or MediaTek for the appropriate system update.

Recommended fix Moderate confidence

Latest available Android 12.0 or higher with March 2022 or later Android Security Patch Level

  1. Check the device manufacturer's security update documentation or support site for the availability of the ALPS07085540 patch
  2. Verify the device has received the Android Security Patch Level that includes the MediaTek camera ISP fix (typically March 2022 or later)
  3. If the patch is not available, contact the device manufacturer (OEM) for firmware update scheduling
  4. Ensure the device is updated to the latest available Android security update for version 12.0 or later

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

Fix this in Android Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA4.0 h
18.0 hours of engineering $3,040
Get help mitigating

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 locally
dbcve dependency scanner

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