CVE-2022-22100
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 multimedia due to improper check on received export descriptors in Snapdragon Auto
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 · low confidenceMemory corruption vulnerability in the multimedia subsystem of Qualcomm Snapdragon Auto automotive chipsets. The issue stems from improper validation of received export descriptors, which could allow an attacker to trigger memory corruption through specially crafted multimedia data, potentially leading to code execution or denial of service.
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
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/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 Qualcomm chipset modelCheck the vehicle system documentation, infotainment system info, or use OEM diagnostic tools to determine the exact Qualcomm Snapdragon Auto chipset model (e.g., Apq8096au, Qca6564a, etc.)Affected if The chipset model matches one of the affected models: Apq8096au, Qam8295p, Qca6564a, Qca6564au, Qca6574a, Qca6574au, Qca6696, or Sa6145p
-
Obtain the firmware versionContact the automotive OEM or tier-1 supplier to request the installed firmware version information for the multimedia subsystem. Use any available OEM diagnostic or infotainment system info screens if accessible.Affected if The firmware version cannot be confirmed as patched, or the OEM has not issued a patch for this CVE (all versions of affected chipsets are vulnerable)
-
Confirm multimedia subsystem is in useVerify that the vehicle infotainment or multimedia system is operational and processes multimedia data (audio, video, or connected media devices)Affected if The multimedia subsystem is active and processes external multimedia content, which is the attack vector for this vulnerability
You are affected if your vehicle or system uses one of the listed Qualcomm Snapdragon Auto chipsets and the OEM has not confirmed applying the vendor-supplied firmware patch for CVE-2022-22100.
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 firmware updates from the automotive OEM or tier-1 supplier that incorporate the Qualcomm patch for this vulnerability. Coordinate with the vehicle manufacturer to schedule the update in accordance with their maintenance processes.
- Consultation8.0 h
- Implementation4.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 $9,856.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-22100 — 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-22100 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