CVE-2022-25658
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 due to incorrect pointer arithmetic when attempting to change the endianness in video parser function 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 confidenceA memory corruption vulnerability exists in the video parser component of Qualcomm Snapdragon chipsets. The flaw stems from incorrect pointer arithmetic when the parser attempts to change endianness during video data processing. This improper pointer manipulation can lead to out-of-bounds memory access, potentially allowing arbitrary code execution.
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 modelCheck the device specifications or system information to determine the Qualcomm Snapdragon or Qualcomm chipset model. Look for model numbers such as Apq8009, Apq8009w, Apq8017, Apq8053, Apq8096au, Aqt1000, Ar8031, or Csra6620.Affected if The device uses any of the listed affected chipset models (Apq8009, Apq8009w, Apq8017, Apq8053, Apq8096au, Aqt1000, Ar8031, or Csra6620).
-
Check firmware versionRetrieve the current firmware version from the device settings, system diagnostics, or by querying the bootloader/Baseband version. Compare against any available patch versions from the vendor.Affected if The firmware version is older than any available vendor patches, or no patch has been applied.
-
Verify video processing capabilityDetermine if the device has video playback or video processing functionality enabled. This can be checked by examining installed media players, video codecs, or video capture features in the system.Affected if The device has an active video parser component that processes video data, as the vulnerability exists in the video parser.
-
Check for untrusted video input sourcesAudit the device or network configuration to identify if it accepts video input from untrusted or external sources such as unverified streaming URLs, untrusted video files, or external video feeds.Affected if The device processes video from untrusted or unverified sources, which could trigger the vulnerable code path.
A user is affected if their device contains any of the affected Qualcomm chipset models (Apq8009, Apq8009w, Apq8017, Apq8053, Apq8096au, Aqt1000, Ar8031, or Csra6620) and the firmware lacks vendor patches, particularly if the device processes video data from any source.
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-supplied patches/firmware updates from Qualcomm or device OEMs. Until patches are available, minimize exposure by restricting untrusted video input sources and keeping affected devices behind network segmentation.
- Consultation8.0 h
- Implementation16.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 $13,312.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-25658 — 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-25658 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