CVE-2025-21428
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 occurs while connecting a STA to an AP and initiating an ADD TS request from the AP to establish a TSpec session.
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 WiFi stack during TSpec session establishment. When an Access Point sends an ADD TS (Add Traffic Stream) request to a connecting Station to establish a TSpec session, improper handling of the request leads to memory corruption. This could allow remote code execution or denial of service on the affected device.
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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Identify device platformCheck the device hardware model or system information to determine if it uses one of the affected Qualcomm Snapdragon platforms: 439, 625, 626, 632, 820 Automotive, Auto 5G Modem RF, X12 LTE Modem, or X35 5G Modem RF SystemAffected if The device runs on any of the listed Snapdragon platforms
-
Confirm WiFi interface is activeCheck if WiFi is enabled on the device via system settings, network configuration, or by running commands like 'ip link show' or 'iwconfig' to list wireless interfacesAffected if WiFi is enabled and the device connects to wireless networks
-
Check TSpec/QoS configurationInspect the WiFi access point or station configuration for TSpec (Traffic Stream) or QoS (Quality of Service) settings. This may be in the wireless router settings under QoS/TSPEC options, or via WiFi client configuration toolsAffected if TSpec or QoS features are enabled on the WiFi interface
-
Verify firmware versionCheck the current firmware version of the WiFi chipset or modem using vendor-specific diagnostic tools, AT commands, or system firmware information utilitiesAffected if The firmware version matches the affected platform list (note: all versions are currently considered affected)
If the device uses an affected Snapdragon platform, has WiFi enabled, and TSpec/QoS features are active, the environment is likely vulnerable to this memory corruption flaw during TSpec session establishment.
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/software patches for the WiFi stack. Until patches are available, consider disabling TSpec/QoS features on vulnerable APs or restricting network access to trusted devices.
- Consultation4.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-21428 — 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-2025-21428 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