CVE-2022-22101
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 · uneditedDenial of service in multimedia due to uncontrolled resource consumption while parsing an incoming HAB message 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 · moderate confidenceA denial of service vulnerability exists in the multimedia subsystem of Snapdragon Auto processors due to uncontrolled resource consumption during parsing of incoming HAB (High Assurance Boot) messages. An attacker can trigger this vulnerability by sending a specially crafted HAB message, causing the system to consume excessive resources and potentially crash.
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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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 Snapdragon processor modelCheck system information or hardware specs to determine the exact Snapdragon Auto processor model (e.g., Apq8096au, Qam8295p, Qca6564a, Qca6564au, Qca6574a, Qca6574au, Qca6696, or Sa6145p)Affected if The system uses any of the following processors: Apq8096au, Qam8295p, Qca6564a, Qca6564au, Qca6574a, Qca6574au, Qca6696, or Sa6145p
-
Confirm firmware versionRetrieve the firmware version from the device (typically via diagnostic tools, boot logs, or manufacturer documentation)Affected if Any firmware version is installed on the affected processor models (all versions are vulnerable)
-
Verify multimedia subsystem is activeCheck if the multimedia subsystem component is loaded and running on the systemAffected if The multimedia subsystem is enabled and processing media content
-
Check HAB message handling capabilityExamine system logs or configuration to determine if HAB (High Assurance Boot) message parsing is active within the multimedia componentAffected if HAB message processing is enabled in the multimedia subsystem
If the system uses any of the affected Snapdragon Auto processor models (Apq8096au, Qam8295p, Qca6564a, Qca6564au, Qca6574a, Qca6574au, Qca6696, or Sa6145p) with the multimedia subsystem and HAB message handling active, the environment is vulnerable to CVE-2022-22101.
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 the vendor-supplied firmware update for Snapdragon Auto processors. If no update is available, implement input validation and resource limits on HAB message processing within the multimedia component.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-22101 — 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-22101 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