CVE-2022-25653
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 · uneditedInformation disclosure in video due to buffer over-read while processing avi file in Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, 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 confidenceA buffer over-read vulnerability in the video processing component allows disclosure of sensitive memory contents when parsing specially crafted AVI files. The vulnerability stems from insufficient bounds checking during AVI file parsing in the Snapdragon firmware, potentially exposing heap or stack memory beyond the allocated buffer.
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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
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 modelCheck the device specifications or system information to determine the exact Qualcomm Snapdragon chipset model (e.g., Apq8053, Aqt1000, Msm8953, Qca6390, Qca6391, Qca6420, Qca6426, or Qca6430)Affected if The chipset matches one of the affected models: Apq8053, Aqt1000, Msm8953, Qca6390, Qca6391, Qca6420, Qca6426, or Qca6430
-
Check the firmware versionAccess the device firmware settings or system firmware information to retrieve the current firmware version for the identified Qualcomm chipsetAffected if The firmware version is any version (the advisory indicates all versions are affected)
-
Verify AVI file processing capabilityCheck if the device or application supports opening, playing, or processing AVI video files. This may be through a media player, video editing software, or file parsing library on the deviceAffected if AVI file processing functionality is available and enabled on the device or in the software using the chipset
-
Inspect video processing component logsIf available, review system or application logs for any anomalies, crashes, or memory access errors when parsing AVI files. On affected devices, the vulnerability may produce unexpected behavior during AVI handlingAffected if The device processes AVI files and exhibits unusual behavior or memory access patterns during AVI file operations
A user is affected if their device contains one of the listed Qualcomm chipsets (Apq8053, Aqt1000, Msm8953, Qca6390, Qca6391, Qca6420, Qca6426, or Qca6430) and the device or its software processes AVI files.
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-provided firmware updates from Qualcomm for affected Snapdragon products. Until patches are available, exercise caution when opening AVI files from untrusted sources.
- Consultation8.0 h
- Implementation24.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 $15,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-25653 — 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-25653 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