dbcve.org
AndroidOperating system · Google

CVE-2022-32653

MEDIUM · 6.7 CVSS v3.1 Published 2023-01-03
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 mtk-aie, there is a possible use after free due to a logic error. This could lead to local escalation of privilege with System execution privileges needed. User interaction is not needed for exploitation. Patch ID: ALPS07262518; Issue ID: ALPS07262518.

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 use-after-free vulnerability exists in MediaTek's mtk-aie (AI Engine) component due to a logic error. An attacker with local System-level access can exploit this memory corruption issue to escalate privileges. No user interaction is required for exploitation.

MitigationApply the MediaTek patch ALPS07262518 through firmware update from the device OEM. This is a底层 firmware issue requiring vendor coordination.

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:= 12.0= 13.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. Check Android version matches affected releases
    Run 'getprop ro.build.version.release' or check Settings > About Phone > Android version. The affected versions are exactly 12.0 and 13.0.
    Affected if The reported Android version is 12.0 or 13.0 specifically.
  2. Verify device uses a MediaTek SoC
    Run 'getprop ro.hardware' or check /proc/cpuinfo for MediaTek or MTK identifiers. This vulnerability exists in MediaTek's mtk-aie (AI Engine) component, which only exists on MediaTek chipsets.
    Affected if The device hardware is not MediaTek-based (the mtk-aie component is MediaTek-specific).
  3. Confirm mtk-aie driver is present
    Check for the mtk-aie kernel module or driver presence. Look in /proc/modules, /sys/module/, or run 'lsmod | grep aie' if the device supports module listing. Also check 'getprop | grep mtk.aie' for related system properties.
    Affected if The mtk-aie driver module is not loaded or does not exist on the device.
  4. Check firmware patch level
    Run 'getprop ro.build.version.security_patch' to view the security patch date. Compare against the MediaTek patch ALPS07262518 release timeline from the device OEM.
    Affected if The security patch level is older than the patch that addresses ALPS07262518.

The device is affected only if it runs Android 12.0 or 13.0, uses a MediaTek chipset with the mtk-aie AI Engine component present, and has a firmware patch level predating the ALPS07262518 fix.

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 MediaTek patch ALPS07262518 through firmware update from the device OEM. This is a底层 firmware issue requiring vendor coordination.

Recommended fix High confidence

Android Security Bulletin January 2023 or later (patch level 2023-01-01 or higher)

  1. Check your Android device's build number in Settings > About Phone > Build Number
  2. Contact your device OEM or carrier for the availability of the January 2023 Android Security Bulletin patch or later
  3. If available, apply the system update containing the ALPS07262518 patch
  4. Alternatively, if using a MediaTek-based device, check MediaTek's firmware update channel for the patch
Caveat Patches are cumulative; applying security updates should not introduce functional breaking changes but verify OEM-specific release notes

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-32653 — 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-32653 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