CVE-2022-20064
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 ccci, there is a possible leak of kernel pointer due to an incorrect bounds check. This could lead to local information disclosure with System execution privileges needed. User interaction is not needed for exploitation. Patch ID: ALPS06108617; Issue ID: ALPS06108617.
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 confidenceIn the ccci kernel driver (related to cellular/modem communication on MediaTek-based Android devices), an incorrect bounds check allows leaking kernel pointers to userspace. This information disclosure could aid in bypassing kernel address space layout randomization (KASLR). The vulnerability is locally exploitable with System-level privileges and requires no 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
- 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.
-
Verify Android versionCheck the Android OS version in Settings > About Phone > Android version, or run 'getprop ro.build.version.release' in a shellAffected if The version is 10.0, 11.0, or 12.0 - only these versions are affected by this CVE
-
Confirm MediaTek chipset presenceRun 'getprop ro.hardware' or check /proc/cpuinfo to identify the SoC vendor; the ccci driver is specific to MediaTek-based devicesAffected if The device uses a MediaTek (rather than Qualcomm or other) chipset, as the ccci driver is MediaTek-specific
-
Check if ccci driver is loadedRun 'ls -la /dev/ccci*' or check kernel module loading status via 'cat /proc/modules | grep ccci' in a root shellAffected if The ccci driver is present and loaded on the device, which is required for the vulnerability to be exploitable
-
Inspect security patch levelRun 'getprop ro.build.version.security_patch' to see the installed security patch date; compare against the vendor patch ALPS06108617Affected if The security patch level is earlier than the vendor fix date, indicating the bounds check flaw may still be present
A user is affected if their Android device runs version 10.0, 11.0, or 12.0, uses a MediaTek chipset with the ccci driver loaded, and lacks the vendor security patch ALPS06108617.
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.
From vendor dataApply vendor patch ALPS06108617 to fix the incorrect bounds check in the ccci driver. As a kernel-level information disclosure, this should be prioritized for patching on affected devices.
- Consultation6.0 h
- Implementation12.0 h
- Testing16.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,520.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-20064 — 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-20064 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