CVE-2025-47403
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 when processing a malformed Fast Transition response frame with an invalid header structure during wireless roaming.
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 confidenceA denial of service vulnerability exists in the wireless roaming stack where processing a malformed Fast Transition (802.11r) response frame with an invalid header structure causes a transient crash or hang. The vulnerability is triggered during wireless roaming when an attacker injects or sends a specially crafted malicious frame that the affected device fails to handle gracefully, leading to a denial of service condition.
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 Qualcomm firmware versionAccess the device's wireless firmware or modem information through vendor-specific commands (for example, 'at+modeminfo' or through the device's administrative interface) and record the firmware version stringAffected if The firmware matches one of the affected products: Snapdragon X65 5g, Snapdragon X72 5g, Snapdragon X75 5g, Srv1h, Srv1m, Sxr2230p, Sxr2250p, or Sxr2330p
-
Confirm 802.11r Fast Transition is enabledCheck the wireless access point or client configuration for 802.11r (Fast BSS Transition) settings. This is typically found in wireless security or roaming settings. Use 'iw list' or the controller GUI to inspect the enabled featuresAffected if 802.11r Fast Transition is currently enabled on the wireless interface
-
Review wireless subsystem crash logsExamine system logs (dmesg, journalctl, or vendor-specific logs) for any recent crashes, hangs, or restarts related to the wireless or roaming subsystem occurring around the time of suspected incidentsAffected if There are recent crash logs or unexpected reboots tied to the wireless roaming stack
-
Check for anomalous roaming behaviorMonitor wireless client associations and roaming events through access point controllers, RADIUS logs, or network monitoring tools for unusual roaming failures or disconnectionsAffected if Unusual patterns of roaming failures or client disconnections are observed, especially during Fast Transition operations
The device is affected if it runs any of the listed Qualcomm firmware versions and has 802.11r Fast Transition enabled, as the vulnerability is triggered by malformed 802.11r response frames during wireless roaming.
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 patches for affected wireless firmware or drivers. If no patch is available, consider network segmentation to limit exposure to untrusted wireless actors and monitor for anomalous roaming activity.
- Consultation8.0 h
- Implementation24.0 h
- Testing16.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $15,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-47403 — 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-47403 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