CVE-2025-21430
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 · uneditedTransient DOS while connecting STA to AP and initiating ADD TS request from AP to establish 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 confidenceThis is a denial-of-service vulnerability in Wi-Fi (802.11) implementations where a transient crash occurs when a wireless station (STA) connects to an access point (AP) and the AP initiates an ADD TS (Add Traffic Stream) request to establish a TSpec (Traffic Specification) session for QoS purposes. The vulnerability lies in the handling of the 802.11e QoS TSpec establishment during association.
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 the wireless hardware/firmware in useExamine your device's network adapters, wireless firmware, or system information to determine if a Qualcomm IoT modem (315 5g), APQ8017, APQ8064au, AQT1000, Ar8031, QCS9100, QEP8111, or QFW7114 is present. Consult the device's documentation or firmware management interface.Affected if The device uses any of the listed Qualcomm firmware products (all versions are affected).
-
Confirm device is operating as a Wi-Fi station (STA)Check the wireless interface configuration to verify the device is functioning as a client/station connecting to an external access point, rather than acting as an AP itself. The vulnerability triggers when the device receives an ADD TS request from an AP.Affected if The device is operating in STA mode and connected to a Wi-Fi access point.
-
Verify WMM/QoS is enabled on the wireless interfaceInspect the wireless interface settings or configuration files for WMM (Wi-Fi Multimedia), QoS, or 802.11e QoS settings. On Linux, use 'iw list' or check wpa_supplicant configuration. On Windows, check adapter properties. On embedded devices, check the WiFi driver or AP configuration.Affected if WMM or 802.11e QoS is enabled on the wireless interface - this feature must be active for the TSpec handling vulnerability to be triggerable.
-
Monitor for wireless service disruptions during associationReview system logs, kernel logs (dmesg), or Wi-Fi driver logs for crashes, resets, or connection failures occurring during or immediately after association with an AP, particularly when QoS/Tspec negotiation takes place.Affected if Crashes, disconnects, or service interruptions occur during the association phase when the AP initiates QoS/TSpec setup.
If your device uses any of the affected Qualcomm firmware products, operates as a Wi-Fi station, and has WMM/QoS enabled, the vulnerability is present in your environment.
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 or driver updates for affected wireless devices. If no patch is available, consider disabling WMM/QoS features on the AP as a temporary workaround.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-21430 — 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-21430 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