CVE-2022-22061
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 · uneditedOut of bounds writing is possible while verifying device IDs due to improper length check before copying the data in Snapdragon Compute, Snapdragon Connectivity, Snapdragon Mobile
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 confidenceMemory corruption vulnerability in Qualcomm Snapdragon chipsets where an out-of-bounds write occurs during device ID verification due to insufficient length validation before copying data into a buffer.
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 model in your deviceCheck your device hardware documentation, system information, or firmware metadata to determine if the chipset matches one of the affected models: Ar8035, Qca6390, Qca6391, Qca6421, Qca6426, Qca6431, Qca6436, or Qca8081Affected if Your device uses any of these Qualcomm chipset models listed in the affected products
-
Determine the firmware version of the Qualcomm chipsetAccess the firmware version through device settings, system diagnostics, or by querying the chipset via available diagnostic interfaces (such as debug logs, bootloader information, or OEM firmware utilities)Affected if The installed firmware version matches any of the affected chipset models regardless of version number (all versions are affected)
-
Verify if device ID verification functionality is present and accessibleExamine firmware configuration, boot logs, or diagnostic capabilities to determine whether the device ID verification code path exists and can be triggered in your specific device implementationAffected if The device ID verification feature is present in the firmware and accessible for execution (the vulnerability exists in this code path regardless of whether it is actively exploited)
-
Check OEM or device vendor security advisoriesReview your device manufacturer's security documentation or support website for any mentions of CVE-2022-22061 affecting your specific device modelAffected if The device vendor has published an advisory or patch for this CVE indicating your device model is impacted
You are affected if your device contains any of the listed Qualcomm chipset models (Ar8035, Qca6390, Qca6391, Qca6421, Qca6426, Qca6431, Qca6436, or Qca8081) regardless of firmware version, as all versions of these chipsets contain the flawed device ID verification code.
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 firmware updates provided by device OEMs or Qualcomm to address the improper length check in the device ID verification code.
- Consultation8.0 h
- Implementation40.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 $20,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-22061 — 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-22061 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