CVE-2022-25708
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 WLAN due to buffer copy without checking size of input while parsing keys in 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 · moderate confidenceBuffer overflow vulnerability in Qualcomm Snapdragon WLAN driver where parsing keys without validating input size allows memory corruption. The lack of bounds checking during key parsing enables an attacker to overwrite adjacent memory, potentially achieving code execution.
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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 WLAN hardware chipsetCheck system information or device manager for the WLAN adapter model. On Linux: 'lspci | grep -i wireless' or 'lshw -C network'. On Windows: 'devmgmt.msc' look under Network adapters. On Android: Check Settings > About Phone > Chipset or use 'lspci' in a terminal emulator.Affected if The chipset matches any of the following: Sd 8 Gen1, Sd888, Sm7450, Wcd9370, Wcd9375, Wcd9380, Wcd9385, or Wcn6750
-
Check WLAN firmware versionQuery the WLAN firmware version through vendor-specific tools. On Linux, use 'iw list' or 'ethtool -i <interface>'. For Android devices, check through 'Settings > About Phone > Software Information > Baseband' or use 'getprop' commands. For access points, check the web interface or CLI for firmware details.Affected if The installed firmware version cannot be verified as patched (all versions listed are affected) and the chipset matches the affected models
-
Verify WLAN key parsing feature is activeConfirm WLAN functionality is enabled and the device is capable of processing wireless keys. Check if WLAN is powered on: 'ip link show' on Linux, or check wireless adapter status in Windows Device Manager. On Android, verify WiFi is enabled in Settings.Affected if WLAN is enabled and the device uses the affected Qualcomm WLAN firmware for key processing
-
Check for vendor firmware update availabilityConsult the device manufacturer or Qualcomm documentation for available firmware updates. Check the device support pages or contact the vendor for the specific chipset firmware revision.Affected if No vendor firmware update has been applied and the chipset is on the affected list
A user is affected if their device utilizes any of the listed Qualcomm WLAN chipsets (Sd 8 Gen1, Sd888, Sm7450, Wcd9370-9385, Wcn6750) with the vulnerable firmware and has WLAN functionality enabled for key parsing.
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 firmware updates from Qualcomm and device manufacturers. Prioritize patching mobile devices and access points with available updates.
- Consultation16.0 h
- Implementation8.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,640.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-25708 — 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-25708 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