CVE-2025-47328
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 power control requests with invalid antenna or stream values.
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 confidenceThis is a denial-of-service vulnerability in power control request processing. The vulnerability is triggered when processing requests containing invalid antenna or stream values, causing a transient DOS condition. The issue likely stems from missing or insufficient input validation before processing power control parameters.
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 device firmware and platform modelAccess the device management interface (web UI, CLI, or SNMP) and retrieve the firmware version and hardware model information. Common paths: check 'System Information' or run 'show version' command.Affected if The firmware version corresponds to any of these platforms: Qualcomm Fastconnect 7800, Immersive Home 3210, Immersive Home 326, Ipq5300, Ipq5302, Ipq5312, Ipq5332, or Ipq5424.
-
Determine if power control request feature is exposedReview device configuration or API endpoints to check whether the power control request handler is accessible. This may be via WiFi management interfaces, vendor-specific APIs, or debugging interfaces.Affected if The power control feature is enabled and accessible (for example, via wireless management daemon, API, or CLI command that accepts antenna/stream parameters).
-
Check for recent unexpected resets or crash logsReview system logs, kernel logs, or boot logs for sudden reboots, assertion failures, or crashes that coincide with power control requests. Use 'dmesg', 'logread', or vendor-specific log commands.Affected if The device exhibits unexpected resets or DOS symptoms after processing power control requests with malformed antenna or stream values.
If the device runs any version of the listed Qualcomm platforms and has the power control feature accessible, it is likely affected; the vulnerability exists in all versions and is triggered by invalid antenna or stream values in power control requests.
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 proper input validation for antenna and stream values in power control request handlers to ensure values fall within acceptable ranges. Organizations should monitor vendor advisories for patched firmware/software releases.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-47328 — 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-47328 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