CVE-2025-47395
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 parsing a WLAN management frame with a Vendor Specific Information Element.
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 parsing logic for WLAN management frames containing Vendor Specific Information Elements (IE). When a malformed or crafted Vendor Specific IE is encountered during frame processing, the parser enters an error state or crashes, causing a transient service disruption.
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 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
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:A/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 Qualcomm Wcn7861 Wi-Fi hardwareCheck system hardware information using commands like 'lspci', 'lsusb', or platform-specific tools to list wireless network adapters. Look for entries containing 'Wcn7861' or 'Qualcomm' in the wireless device description.Affected if The system contains a Qualcomm Wcn7861 wireless chip
-
Verify WLAN interface is activeCheck if a wireless interface exists and is up using 'ip link show' or 'iwconfig'. Look for interfaces like wlan0, wlp, or similar wireless interfaces.Affected if A wireless interface is present and enabled (UP state)
-
Check Wcn7861 firmware versionQuery the wireless firmware version through driver interfaces. On Linux, check /sys/class/net/*/device/firmware_version or use 'ethtool -i' on the wireless interface. Alternatively, use 'iw list' or vendor-specific tools provided by the system manufacturer.Affected if The firmware version reported is any version of Qualcomm Wcn7861 (the vulnerability affects all versions)
-
Confirm vendor-specific IE processing is activeThe vulnerability triggers when WLAN management frames with Vendor Specific Information Elements are parsed. This occurs passively during normal wireless operation when the device scans for networks or processes beacon frames/probe responses.Affected if Wireless scanning or monitoring mode is enabled, allowing the device to process management frames containing Vendor Specific IE
If the system uses Qualcomm Wcn7861 firmware and has WLAN functionality enabled, the environment is affected by this vulnerability.
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 the affected WLAN stack or firmware. If no patch exists, consider disabling WLAN functionality or implementing network filtering to block malformed management frames.
- Consultation2.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,480.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-47395 — 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-47395 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