Memory corruption via invalid SPI address configuration
Published Dec 13, 2022 · Updated Apr 22, 2025
Improper input validation in Qualcomm Snapdragon Mobile and Snapdragon Wearables allows local users to corrupt memory through SPI configuration data. The SPI bus address-configuration reader accepts an improperly validated address configuration, leading to memory corruption. Local access is required, but no privileges or user interaction are required; Qualcomm has not disclosed whether exploitation causes a crash, code execution, or data access.
Summary
What happened
Improper input validation in Qualcomm Snapdragon Mobile and Snapdragon Wearables allows local users to corrupt memory through SPI configuration data. The SPI bus address-configuration reader accepts an improperly validated address configuration, leading to memory corruption. Local access is required, but no privileges or user interaction are required; Qualcomm has not disclosed whether exploitation causes a crash, code execution, or data access.
The record
- CVE
- CVE-2022-25698
- Published
- Dec 13, 2022
- Updated
- Apr 22, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, CWE-20
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 13, 2022CVE publishedPublication date reported by the CVE source.
- Apr 22, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo