CVE-2022-25698
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 SPI buses due to improper input validation while reading address configuration from spi buses in Snapdragon Mobile, 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 · moderate confidenceMemory corruption vulnerability in Snapdragon SPI bus drivers due to improper input validation when reading address configuration from SPI buses. The lack of validation on address parameters allows an attacker to trigger out-of-bounds memory access, potentially leading to arbitrary 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 Qualcomm firmware or chip in useCheck system documentation, bootloader logs, or hardware identifiers to determine if the device uses any of the following firmware: Sd 8 Gen1 5g, Sd429, Sda429w, Sdm429w, Wcd9380, Wcn3610, Wcn3620, or Wcn3660bAffected if The device runs any of the listed Qualcomm firmware variants (Sd 8 Gen1 5g, Sd429, Sda429w, Sdm429w, Wcd9380, Wcn3610, Wcn3620, Wcn3660b)
-
Verify SPI bus driver is present and activeCheck system driver logs, /dev/spi* entries, or kernel module listings (lsmod) for spi driver modules such as spi_qsd, spi_geni, or similar Qualcomm SPI bus driversAffected if SPI bus driver modules (spi_qsd, spi_geni, or vendor-specific SPI drivers) are loaded and active on the system
-
Confirm SPI address configuration reading is enabledReview driver configuration files or examine SPI driver initialization code for address parameter handling functions that read address configuration from SPI busesAffected if The SPI driver includes code paths that read address configuration values directly from SPI bus registers without validation
-
Check for secure boot verification mechanismExamine boot logs or system configuration for secure boot status indicators (e.g., verified boot, dm-verity, AVB)Affected if Secure boot is disabled or not enforcing firmware integrity verification, allowing unmodified vulnerable firmware to run
-
Assess physical access to SPI interfacesInspect hardware for accessible SPI test points, debug headers, or exposed SPI flash chips on the boardAffected if SPI interfaces (test points, flash memory, debug headers) are physically accessible without tampering protection
A system is affected if it runs any of the listed Qualcomm firmware variants (Sd 8 Gen1 5g, Sd429, Sda429w, Sdm429w, Wcd9380, Wcn3610, Wcn3620, Wcn3660b) with the SPI bus driver enabled and has SPI address configuration reading exposed, especially if secure boot is not enforcing firmware integrity.
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-supplied firmware updates for Snapdragon Mobile and Wearable devices. Until patches are available, limit physical access to SPI interfaces and verify firmware integrity through secure boot mechanisms.
- Consultation8.0 h
- Implementation16.0 h
- Testing24.0 h
- Review / QA12.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $16,384.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-25698 — 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-25698 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