CVE-2022-22094
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 Kernel due to race condition while getting mapping reference in Snapdragon Compute, Snapdragon Connectivity, Snapdragon Industrial IOT, 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 confidenceA race condition in the kernel when obtaining a mapping reference leads to memory corruption. The vulnerability exists in Qualcomm Snapdragon chipsets across Compute, Connectivity, Industrial IOT, and Mobile product lines. An attacker with local access could exploit this race condition to corrupt kernel memory, potentially achieving privilege escalation.
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
- High
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:H/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 Qualcomm chipset modelRun `lspci` or check system hardware information for Qualcomm network/adapter components. For mobile/embedded devices, check `/proc/cpuinfo` or device tree files. Look for identifiers: Aqt1000, Qca6390, Qca6391, Qca6420, Qca6421, Qca6426, Qca6430, or Qca6431.Affected if The system contains any of these eight Qualcomm chipset identifiers
-
Retrieve firmware versionCheck the firmware version of the identified Qualcomm component. For wireless adapters, use `iw list`, `ethtool -i`, or vendor-specific tools. For embedded devices, check `/sys/firmware/qca_fw_version` or similar device-specific paths. The method varies by device manufacturer.Affected if A firmware version is returned and matches one of the affected chipset models (all versions are vulnerable)
-
Verify kernel module usageConfirm the Qualcomm kernel driver is loaded. Run `lsmod` and look for Qualcomm-specific modules (often named qca*, ath*, or similar). Also check `dmesg` for Qualcomm driver initialization messages.Affected if A Qualcomm driver module matching the affected chipset is actively loaded or initialized
If the system contains any of the eight listed Qualcomm chipsets (Aqt1000, Qca6390, Qca6391, Qca6420, Qca6421, Qca6426, Qca6430, Qca6431) and the corresponding firmware is running, the environment is affected since all firmware versions are vulnerable.
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 Qualcomm-provided kernel security patch via firmware update from the device/OEM manufacturer. This is a low-level kernel fix requiring vendor-supplied firmware; no user-facing configuration can remediate this vulnerability.
- Consultation8.0 h
- Implementation24.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 $15,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-22094 — 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-22094 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