dbcve.org
Ar8035 FirmwareOperating system · Qualcomm

CVE-2022-25691

HIGH · 7.5 CVSS v3.1 Published 2022-12-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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
Denial of service in Modem due to reachable assertion while processing SIB1 with invalid SCS and bandwidth settings in 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 confidence

Denial of service vulnerability in Qualcomm Snapdragon Mobile modem. The modem crashes when processing SIB1 (System Information Block Type 1) containing invalid Subcarrier Spacing (SCS) and bandwidth configuration settings, which triggers a reachable assertion causing the modem to become unresponsive.

MitigationThis is a firmware-level vulnerability requiring a patch from the device OEM/Qualcomm. The fix involves adding proper validation of SIB1 SCS and bandwidth parameters in the modem firmware before processing to prevent the assertion from being triggered. End users should apply firmware updates from their device manufacturers.

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
Qca8081 FirmwareOperating system
Affected:all versions
Qca8337 FirmwareOperating system
Affected:all versions
Qcn6024 FirmwareOperating system
Affected:all versions
Qcn9024 FirmwareOperating system
Affected:all versions
Sd 8 Gen1 5g FirmwareOperating system
Affected:all versions
Sd480 FirmwareOperating system
Affected:all versions
Sd695 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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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 checks

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

  1. Identify the modem chipset model
    Check the device specifications or use AT commands (such as 'AT+CGMM' or 'AT+CGAINFO') to query the modem chipset. For embedded devices, review the BOM or hardware documentation to identify the Qualcomm chip (Ar8035, Qca8081, Qca8337, Qcn6024, Qcn9024, SD 8 Gen1 5G, SD480, or SD695).
    Affected if The device uses any of the listed Qualcomm chips: Ar8035, Qca8081, Qca8337, Qcn6024, Qcn9024, SD 8 Gen1 5G, SD480, or SD695.
  2. Verify the firmware version
    Query the modem firmware version using vendor-specific AT commands (such as 'AT+CGMR', 'AT+GMR', or through the device's firmware management interface). Compare the version string against the affected product list.
    Affected if The firmware version corresponds to any of the listed affected products, since all versions are vulnerable.
  3. Check for modem unresponsiveness symptoms
    Monitor the modem for sudden loss of connectivity, inability to register on the network, or complete modem failure. Use network monitoring tools or modem status queries (such as 'AT+CREG?' or 'AT+CEREG?') to detect prolonged registration failures.
    Affected if The modem becomes unresponsive or crashes without an obvious cause, especially after network conditions change.
  4. Inspect SIB1 processing logs
    If available, review modem or base station logs for SIB1 (System Information Block Type 1) messages containing invalid Subcarrier Spacing (SCS) or bandwidth configuration values. This may require access to protocol analyzer logs or modem debug output.
    Affected if SIB1 messages with malformed SCS or bandwidth parameters are being processed by the modem.

A user is affected if their device incorporates any of the listed Qualcomm modem chips (Ar8035, Qca8081, Qca8337, Qcn6024, Qcn9024, SD 8 Gen1 5G, SD480, or SD695) and experiences unexplained modem crashes or unresponsiveness, particularly related to SIB1 processing.

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

This is a firmware-level vulnerability requiring a patch from the device OEM/Qualcomm. The fix involves adding proper validation of SIB1 SCS and bandwidth parameters in the modem firmware before processing to prevent the assertion from being triggered. End users should apply firmware updates from their device manufacturers.

Fix this in Ar8035 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA6.0 h
38.0 hours of engineering $6,560
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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