CVE-2026-21381
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 receiving a service data frame with excessive length during device matching over a neighborhood awareness network protocol connection.
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 neighborhood awareness network protocol implementation. When a device receives a service data frame with an excessively long length during the device matching process, it causes a transient service disruption. The vulnerability is triggered by malformed oversized frames during peer device discovery and pairing.
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 versionCheck the system information or firmware inventory for the device. For embedded devices, this may be found via 'cat /proc/firmware_info', 'dmesg | grep firmware', or the device's administrative UI under status or about pages. Compare the firmware name and version against the list: Ar8035, Cologne, Fastconnect 6200, Fastconnect 6700, Fastconnect 6900, Fastconnect 7800, Fwa Gen 3 Ultra, or G2 Gen 1.Affected if The device runs any of the listed Qualcomm firmware products.
-
Determine if neighborhood awareness network protocol is activeCheck the device's network configuration or running services for the neighborhood awareness or device matching protocol. Look for terms like 'neighbor', 'awareness', 'device discovery', 'pairing', 'NAN' (Neighborhood Aware Networking), or similar features in the device settings, running processes, or network interfaces.Affected if The neighborhood awareness network protocol feature is enabled on the device.
-
Verify device discovery and pairing are accessibleInspect whether the device is configured to accept incoming peer device discovery requests or pairing attempts. This may be visible in wireless settings, Bluetooth settings, or network discovery configuration. Check if discovery mode or pairing mode is turned on.Affected if Device discovery or pairing functionality is accessible to other devices on the network.
-
Inspect service data frame handling configurationExamine the device's network stack configuration for any settings related to service data frame processing, frame size limits, or frame validation during device matching. Look for configuration files or settings that control the neighborhood awareness protocol's frame processing behavior.Affected if No frame length validation or bounds checking is configured, or oversized frames are permitted without filtering.
A device is affected if it runs one of the listed Qualcomm firmware products AND has the neighborhood awareness network protocol enabled with device discovery or pairing accessible, particularly when frame validation settings are not enforcing strict length limits.
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 dataImplement strict length validation and bounds checking on incoming service data frames before processing during device matching. Reject or truncate oversized frames with appropriate error handling to prevent resource exhaustion.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-21381 — 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-2026-21381 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