dbcve.org
Ar8035 FirmwareOperating system · Qualcomm

CVE-2022-22067

HIGH · 7.8 CVSS v3.1 Published 2022-09-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
Zero-click

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
Potential memory leak in modem during the processing of NSA RRC Reconfiguration with invalid Radio Bearer Config in Snapdragon Auto, 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 · high confidence

A memory leak vulnerability exists in Qualcomm Snapdragon modem firmware. The leak occurs specifically when the modem processes NSA (Non-Standalone) 5G RRC Reconfiguration messages containing an invalid Radio Bearer Configuration. The memory allocated for handling this malformed message is not properly freed, leading to resource exhaustion over time.

MitigationApply vendor-supplied firmware updates from the device OEM that include the Qualcomm security patch addressing CVE-2022-22067. Users should check with their device manufacturers for available security updates.

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
Ar8035 FirmwareOperating system
Affected:all versions
Qca6390 FirmwareOperating system
Affected:all versions
Qca6391 FirmwareOperating system
Affected:all versions
Qca6421 FirmwareOperating system
Affected:all versions
Qca6426 FirmwareOperating system
Affected:all versions
Qca6431 FirmwareOperating system
Affected:all versions
Qca6436 FirmwareOperating system
Affected:all versions
Qca6574a 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 modem chipset model
    Check the device hardware specifications, system information, or modem firmware details to determine if the chipset is one of: Ar8035, Qca6390, Qca6391, Qca6421, Qca6426, Qca6431, Qca6436, or Qca6574a. This information is typically found in the device datasheet, FCC filing, or by querying the modem via AT commands (e.g., AT+CGMM or manufacturer-specific commands).
    Affected if The device contains any of the listed Qualcomm chipset models (Ar8035, Qca6390, Qca6391, Qca6421, Qca6426, Qca6431, Qca6436, or Qca6574a).
  2. Check the installed modem firmware version
    Query the modem firmware version using vendor-specific commands or through the device operating system. On Linux-based systems, this may involve checking /proc or sysfs entries. On Android, this could be via settings or dialer codes. The method varies by device OEM.
    Affected if Any firmware version is installed on the affected chipset (all versions are vulnerable).
  3. Determine if the device supports and uses NSA 5G
    Check whether the device is configured to connect to 5G networks in NSA (Non-Standalone) mode. This can be verified through network settings, modem logs, or connection status indicators. NSA 5G requires a 4G LTE anchor layer.
    Affected if The device actively uses or is capable of using NSA 5G radio connections.
  4. Monitor modem subsystem memory usage
    If accessible, monitor the modem processor memory consumption over time. On some devices, this may be observable through diagnostic menus, debug logs, or carrier engineering menus. Look for steadily increasing memory usage in the modem subsystem that does not decrease.
    Affected if The modem subsystem shows continuous memory growth without recovery, potentially leading to resource exhaustion.

A device is likely affected if it contains any of the listed Qualcomm modem chipsets (Ar8035, Qca6390, Qca6391, Qca6421, Qca6426, Qca6431, Qca6436, or Qca6574a) and operates on NSA 5G networks, regardless of the installed firmware version.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor-supplied firmware updates from the device OEM that include the Qualcomm security patch addressing CVE-2022-22067. Users should check with their device manufacturers for available security updates.

Fix this in Ar8035 Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation40.0 h
  • Testing24.0 h
  • Review / QA16.0 h
88.0 hours of engineering $15,280
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-22067 — 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-22067 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