CVE-2025-27065
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 a frame with malformed shared-key descriptor.
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 where processing a network frame containing a malformed shared-key descriptor causes a transient service disruption. The vulnerability is triggered during the parsing phase when the shared-key descriptor structure does not conform to expected specifications.
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 firmware versionLocate and retrieve the firmware version information from the device. This is typically accessible through the device management interface, boot logs, or by querying the system information endpoint. For Qualcomm-based devices, check the wireless firmware modules or baseband firmware version strings.Affected if The device runs any version of the listed Qualcomm firmware products (Ar8035, Fastconnect 6800/6900/7800, Immersive Home 3210/326, Ipq5300/5302)
-
Confirm the affected product familyMatch the identified firmware product name against the list of affected products. Verify that the device utilizes Qualcomm wireless or networking firmware components from the affected product families.Affected if The firmware corresponds to any of the eight listed Qualcomm product families
-
Determine if network frame parsing is activeCheck whether the network interface or wireless stack that processes incoming network frames is enabled and operational. This involves verifying the status of the wireless or networking service that handles frame parsing.Affected if The network frame processing component that includes shared-key descriptor parsing is enabled and actively processing frames
-
Verify shared-key descriptor handling is exposedInspect the device configuration to determine if it accepts and processes network frames containing shared-key descriptors. This typically involves checking wireless security configuration parsers or network protocol handlers.Affected if The device configuration allows processing of frames with shared-key descriptor structures
-
Check for crash or disruption logsReview system logs, kernel logs, or network service logs for evidence of recent service disruptions, crashes, or parsing errors that could indicate exploitation of this vulnerability.Affected if Logs show unexpected service disruptions, parsing failures, or crashes correlated with network frame processing events
The environment is affected if the device runs any version of the listed Qualcomm firmware products and has network frame processing with shared-key descriptor parsing enabled.
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 robust input validation and bounds checking on shared-key descriptor fields within the frame parsing logic to reject malformed frames before processing.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-27065 — 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-27065 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