CVE-2025-21463
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 processing the EHT operation IE in the received beacon frame.
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 Wi-Fi device firmware where processing the EHT (802.11be) Operation Information Element in received beacon frames can cause a transient DOS condition. An attacker within radio range can exploit this by sending a specially crafted beacon frame containing a malformed EHT Operation IE.
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 Wi-Fi chipset modelDetermine the Wi-Fi hardware by reviewing system device information, network adapter details, or hardware specifications. On Linux, use commands like 'lspci -v' or 'lsusb' for network interfaces, or check the device documentation for the chipset model.Affected if The device uses any of the following Qualcomm chipsets: Ar8035, Csr8811, Fastconnect 6700, Fastconnect 6900, Fastconnect 7800, Qca4024, Qca6391, or Qca6554a
-
Confirm firmware versionRetrieve the installed firmware version using vendor-specific tools or system interfaces. On Linux systems, 'ethtool -i <interface>' or reading /sys/class/net/<interface>/device/firmware_version may expose firmware information. Check the Wi-Fi device management interface if available.Affected if The detected firmware corresponds to any of the affected Qualcomm chipset models listed (all versions are impacted)
-
Check if 802.11be (EHT) is enabledVerify whether EHT support is active on the wireless interface. Use 'iw list' to examine supported bands and 802.11 features, or check the device's wireless configuration settings. Look for 802.11be or EHT listed in the supported interface types.Affected if 802.11be (EHT) support is enabled and operational on the device, making it susceptible to malformed beacon frame processing
A device is affected if it runs any firmware version on the listed Qualcomm chipsets and has EHT/802.11be functionality enabled, allowing it to process EHT Operation Information Elements in beacon frames.
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 updates for affected Wi-Fi devices. As an interim compensating control, disable 802.11be (EHT) support on vulnerable devices if operational requirements permit, or segregate EHT-capable devices on separate network segments.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.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 $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-21463 — 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-21463 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