dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 26 Dec 2023.
Apq8053 FirmwareOperating system · Qualcomm

CVE-2022-22071

HIGH · 7.8 CVSS v3.1 Published 2022-06-14
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
96/100
Remediation priority · Urgent
In the wild Zero-click Patch available

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 · unedited
Possible use after free when process shell memory is freed using IOCTL munmap call and process initialization is in progress in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music

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 · high confidence

A use-after-free vulnerability in Qualcomm Snapdragon chipsets allows memory corruption when process shell memory is freed via an IOCTL munmap call while process initialization is simultaneously in progress. This kernel-level flaw could enable local privilege escalation or unexpected behavior.

MitigationApply the vendor-provided firmware/security patch from Qualcomm to affected Snapdragon chipset implementations; coordinate with original equipment manufacturers for deployment.

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 data
Apq8053 FirmwareOperating system
Affected:all versions
Ar8031 FirmwareOperating system
Affected:all versions
Ar8035 FirmwareOperating system
Affected:all versions
Csra6620 FirmwareOperating system
Affected:all versions
Csra6640 FirmwareOperating system
Affected:all versions
Mdm9150 FirmwareOperating system
Affected:all versions
Msm8953 FirmwareOperating system
Affected:all versions
Qca6174a FirmwareOperating system
Affected:all versions

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the Qualcomm Snapdragon processor model in your device
    Check system information, device specs, or /proc/cpuinfo (on Android: Settings > About Phone > Chipset/Processor, or run 'getprop ro.hardware' or 'cat /proc/cpuinfo' via ADB)
    Affected if The processor model matches one of: Apq8053, Ar8031, Ar8035, Csra6620, Csra6640, Mdm9150, Msm8953, or Qca6174a
  2. Determine the firmware version of the Qualcomm component
    Check the firmware/baseband version via Settings > About Phone > Build Number, or run 'getprop ro.build.version.all' or 'cat /proc/version' (on Android: 'getprop' commands via ADB shell)
    Affected if The firmware version cannot be determined or is listed as 'all versions' for the affected models - meaning any version of the listed firmware is vulnerable
  3. Confirm the device uses the affected Qualcomm component
    Review device documentation, manufacturer specifications, or use system profiling tools (like CPU-Z, Device Info HW) to verify the exact chipset and modem/firmware variant
    Affected if The device firmware component (modem, radio, or processor firmware) corresponds to any of the listed affected Qualcomm firmware products

You are affected if your device contains any of the listed Qualcomm firmware components (Apq8053, Ar8031, Ar8035, Csra6620, Csra6640, Mdm9150, Msm8953, or Qca6174a) regardless of version, as all versions of these firmwares contain the vulnerability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Patch available Apply the vendor patch
Vendor patch www.qualcomm.com →
Interim mitigation

Apply the vendor-provided firmware/security patch from Qualcomm to affected Snapdragon chipset implementations; coordinate with original equipment manufacturers for deployment.

Recommended fix Moderate confidence
  1. Contact your device OEM (Original Equipment Manufacturer) to obtain firmware updates addressing CVE-2022-22071
  2. Apply the OEM-provided firmware update to affected devices
  3. Verify the firmware update has been successfully applied by checking the system firmware version
Caveat Firmware updates may require device downtime and should be tested in a staging environment before production deployment

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Apq8053 Firmware Exploited in the wild — priority engagement
  • Consultation10.0 h
  • Implementation4.0 h
  • Testing12.0 h
  • Review / QA6.0 h
32.0 hours of engineering $5,600
Get it fixed fast

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-22071 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-22071 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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