CVE-2022-22086
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 · uneditedMemory corruption in video due to double free while parsing 3gp clip with invalid meta data atoms in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables
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 confidenceMemory corruption vulnerability caused by a double-free condition when parsing 3gp video files containing invalid metadata atoms. The flaw exists in the video parsing component of Snapdragon chipset firmware and could allow remote code execution via crafted 3gp files.
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 dataall versionsall versionsall versionsall versionsall versionsall versionsall versionsall versionsCVSS 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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.
-
Identify the chipset modelDetermine the specific Qualcomm chipset or firmware model running on the device. This is typically found in device specifications, system information, or firmware build details.Affected if The chipset model matches one of the following: Apq8009w, Apq8017, Apq8053, Apq8096au, Aqt1000, Ar8031, Csra6620, or Csra6640.
-
Confirm firmware vendorVerify that the firmware is Qualcomm-based and that the video parsing component is present. This may be documented in the device firmware release notes or system modules list.Affected if The device runs Qualcomm firmware with the video parsing component included.
-
Determine if 3gp video processing is enabledCheck whether the device has video playback capability for 3gp files enabled. This can be confirmed by testing 3gp file playback or reviewing media codec configurations.Affected if 3gp video file parsing and playback functionality is available on the device.
-
Assess exposure to untrusted 3gp filesReview how the device handles 3gp files - whether it can receive them from external sources such as messaging apps, browsers, or file transfers.Affected if The device can process 3gp files from untrusted sources such as received media files, downloads, or attachments.
The device is affected if it runs any of the listed Qualcomm chipset firmware versions (Apq8009w, Apq8017, Apq8053, Apq8096au, Aqt1000, Ar8031, Csra6620, Csra6640) and has the capability to parse 3gp video files, since the double-free flaw triggers when processing crafted 3gp files with invalid metadata atoms.
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 firmware updates for affected Snapdragon devices when available; avoid processing untrusted 3gp files until patches are deployed.
- Consultation8.0 h
- Implementation40.0 h
- Testing24.0 h
- Review / QA16.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $24,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-22086 — 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-22086 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