CVE-2022-26471
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 telephony, there is a possible escalation of privilege due to a parcel format mismatch. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation. Patch ID: ALPS07319121; Issue ID: ALPS07319121.
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 confidenceA parcel format mismatch in the Android telephony subsystem allows a local attacker to escalate privileges without additional execution privileges or user interaction. The vulnerability exists in inter-process communication where data serialization/deserialization between telephony components uses mismatched parcel formats, potentially allowing privilege escalation.
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= 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.
-
Verify Android versionCheck the device Android version in Settings > About Phone > Android version, or run 'getprop ro.build.version.release' via ADBAffected if The device is running Android 12.0 exactly (not 12.0 with updates, not other 12.x versions)
-
Confirm telephony subsystem is activeVerify the device has telephony capabilities and the radio/ril daemon is running. Check with 'ps -A | grep rild' or check for telephony processes in Settings > Apps > Show system processesAffected if The device lacks active telephony functionality, the vulnerability does not apply since it targets the telephony IPC mechanism
-
Check current patch levelCheck the Android security patch level in Settings > About Phone > Security patch level, or run 'getprop ro.build.version.security_patch' via ADBAffected if The security patch level is earlier than the vendor fix ALPS07319121; however without a known released patch date, compare against your OEM's published Android 12.0 security updates
The device is affected only if it runs exactly Android 12.0 with telephony subsystem active and lacks the vendor-specific telephony patch (ALPS07319121).
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 (ALPS07319121) from the device/OEM manufacturer. This is a system-level telephony fix that requires updating the affected Android device to a version containing the patched ALPS telephony component.
- Contact MediaTek directly or check corp.mediatek.com for the ALPS07319121 patch and apply it through your device manufacturer's security update channel
- Ensure your device receives the latest Android security patch update, as this vulnerability is addressed in MediaTek's monthly security bulletins
- If your device manufacturer has released an update containing this fix, apply it through your device's system update mechanism
- Verify the patch has been applied by checking your Android security patch level in Settings > About Phone > Security Patch Level
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,936.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-26471 — 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-26471 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