CVE-2022-25682
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 MODEM UIM due to usage of out of range pointer offset while decoding command from card in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables
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 confidenceMemory corruption vulnerability in the MODEM UIM (SIM card) component of Qualcomm Snapdragon chipsets. The issue occurs due to an out-of-range pointer offset being used while decoding commands from the SIM card, leading to memory corruption that could allow code execution or denial of service.
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 chipset modelCheck the device specifications, system information, or modem firmware identification to determine if the chipset is one of: Apq8009, Apq8009w, Apq8017, Apq8037, Apq8052, Apq8056, Apq8076, or Apq8096au. This may be listed in /proc/cpuinfo, device docs, or modem AT command responses.Affected if The device uses any of the listed Qualcomm APQ chipset models (all versions are affected).
-
Verify the modem UIM component is presentConfirm the device has an active modem with UIM (SIM card) capability. This is typically present on any device with cellular/SIM functionality. Check via modem diagnostic interfaces or AT commands (e.g., AT+CGMM or AT+CGEQ).Affected if The device has cellular connectivity and a SIM card interface using the Qualcomm modem subsystem.
-
Check for unusual modem behaviorMonitor modem logs, UIM (SIM) status, and modem crash dumps for signs of memory corruption: unexpected resets, SIM recognition failures, or memory access errors. Review /var/log/messages, modem debug logs, or vendor diagnostic tools.Affected if There are recurring SIM/UIM errors, unexpected modem restarts, or memory corruption indicators in modem logs.
You are affected if your device uses any of the listed Qualcomm APQ chipsets (Apq8009, Apq8009w, Apq8017, Apq8037, Apq8052, Apq8056, Apq8076, Apq8096au) with cellular/SIM capability, as all firmware versions of these chipsets contain the vulnerable MODEM UIM command decoding component.
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 vendor-provided firmware updates from Qualcomm and device OEMs that address the UIM command decoding pointer validation. Until patches are available, monitor for unusual modem behavior and restrict physical access to the SIM card interface.
- Consultation8.0 h
- Implementation4.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 $9,856.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-25682 — 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-25682 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