dbcve.org
Apq8009 FirmwareOperating system · Qualcomm

CVE-2022-25659

CRITICAL · 9.8 CVSS v3.1 Published 2022-09-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
Memory corruption due to buffer overflow while parsing MKV clips with invalid bitmap size 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 · high confidence

A buffer overflow vulnerability exists in the MKV (Matroska) video parsing code within Qualcomm Snapdragon chipsets. The vulnerability is triggered when parsing MKV video clips containing invalid bitmap size dimensions, leading to memory corruption. This is a classic input validation failure where the parser does not properly validate size parameters before allocating buffers or copying data.

MitigationApply vendor-supplied firmware updates for affected Snapdragon devices. Until patches are available, restrict parsing of MKV files from untrusted sources and monitor for vendor security advisories.

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
Apq8009 FirmwareOperating system
Affected:all versions
Apq8009w FirmwareOperating system
Affected:all versions
Apq8017 FirmwareOperating system
Affected:all versions
Apq8053 FirmwareOperating system
Affected:all versions
Apq8096au FirmwareOperating system
Affected:all versions
Aqt1000 FirmwareOperating system
Affected:all versions
Ar8031 FirmwareOperating system
Affected:all versions
Csra6620 FirmwareOperating system
Affected:all versions

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the chipset model
    Check the processor/hardware information on the device. On Android, use 'getprop' or check /proc/cpuinfo. On embedded Linux, check /proc/cpuinfo or dmesg for Qualcomm module identifiers.
    Affected if The chipset model is one of: Apq8009, Apq8009w, Apq8017, Apq8053, Apq8096au, Aqt1000, Ar8031, or Csra6620.
  2. Verify MKV parsing capability exists
    Check if the device has a video player or media parsing component that supports MKV container format. Look for video decoder libraries, mediacodec entries, or check the firmware image for libavformat, MKV, or Matroska parsing modules.
    Affected if The device includes MKV (Matroska) video parsing functionality.
  3. Confirm firmware version
    Query the firmware version through vendor-specific interfaces (getprop on Android, /proc/version, or vendor AT commands for modems). Compare against any available patch information from the vendor.
    Affected if The firmware version matches an affected chipset listed and no vendor security patch for CVE-2022-25659 has been applied.
  4. Check for untrusted MKV input handling
    Audit any applications or services that process MKV files. Look for video players, transcoding tools, or media servers that accept MKV input from external or untrusted sources.
    Affected if The device processes MKV files from untrusted or external sources through any onboard media handling component.

A device is affected if it uses one of the listed Qualcomm chipset models (Apq8009, Apq8009w, Apq8017, Apq8053, Apq8096au, Aqt1000, Ar8031, or Csra6620) and includes MKV video parsing capability, particularly when handling MKV files from untrusted sources.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor-supplied firmware updates for affected Snapdragon devices. Until patches are available, restrict parsing of MKV files from untrusted sources and monitor for vendor security advisories.

Fix this in Apq8009 Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation24.0 h
  • Testing16.0 h
  • Review / QA8.0 h
56.0 hours of engineering $9,760
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-25659 — 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-25659 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