dbcve.org
Apq8009 FirmwareOperating system · Qualcomm

CVE-2022-25688

CRITICAL · 9.8 CVSS v3.1 Published 2022-09-16
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 in video due to buffer overflow while parsing ps video clips 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

Buffer overflow vulnerability in video parsing logic for PS (Program Stream) video clips in Qualcomm Snapdragon chipsets. The memory corruption occurs during parsing of malformed video files, potentially allowing remote code execution.

MitigationApply vendor-supplied firmware updates from Qualcomm and device manufacturers to address the buffer overflow in video parsing. Until patches are available, limit exposure by avoiding untrusted video sources.

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 Qualcomm chipset model in the system
    Check system information using commands like 'lspci', 'lsusb', 'cat /proc/cpuinfo', or check device tree files (/proc/device-tree/) to identify if the system contains one of the affected chipsets: Apq8009, Apq8009w, Apq8017, Apq8053, Apq8096au, Aqt1000, Ar8031, or Csra6620
    Affected if The system contains any of the listed Qualcomm chipset models (Apq8009, Apq8009w, Apq8017, Apq8053, Apq8096au, Aqt1000, Ar8031, Csra6620)
  2. Check the firmware version of the identified Qualcomm chipset
    Query the chipset firmware version through manufacturer-specific tools, /sys/firmware/devicetree, or vendor management interfaces. For embedded devices, check /proc/qsee_version, dmesg logs, or consult device documentation for firmware version retrieval methods
    Affected if The chipset firmware version matches one of the affected models (all firmware versions are affected for each listed chipset)
  3. Determine if video playback functionality is enabled
    Check if video decoding or playback modules are loaded or active on the system. Look for video-related kernel modules (via 'lsmod'), services, or configurations that enable media processing. Check for applications or daemons that handle video file parsing
    Affected if Video playback or video parsing functionality is enabled and the system uses the affected Qualcomm chipset
  4. Verify if PS (Program Stream) video format support is present
    Check system capabilities for MPEG Program Stream support. Examine video codec support configuration,ffmpeg/libav output, or media framework capabilities (e.g., via 'gst-inspect' for GStreamer, or MediaCodec info on Android) to determine if PS video format parsing is available
    Affected if PS video format parsing capability exists and the system runs on the affected Qualcomm chipset firmware

A system is affected if it contains any of the listed Qualcomm chipset models (Apq8009, Apq8009w, Apq8017, Apq8053, Apq8096au, Aqt1000, Ar8031, Csra6620) with video parsing functionality enabled, as all firmware versions of these chipsets contain the vulnerability.

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 from Qualcomm and device manufacturers to address the buffer overflow in video parsing. Until patches are available, limit exposure by avoiding untrusted video sources.

Fix this in Apq8009 Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
36.0 hours of engineering $6,400
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $10,240.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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