CVE-2025-47392
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 · uneditedMemory corruption when decoding corrupted satellite data files with invalid signature offsets.
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 confidenceMemory corruption vulnerability in satellite data file decoder due to insufficient validation of signature offsets in corrupted files, allowing potential code execution or denial of service via malformed file parsing.
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
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 platform or chipset modelCheck the device documentation, system information, or firmware metadata to confirm the exact Qualcomm product name and model numberAffected if The platform matches any of these: 5g Fixed Wireless Access Platform, Ar8035, Csra6620, Csra6640, Fastconnect 6200, Snapdragon 690 5g, Snapdragon 695 5g, or Snapdragon 7 Gen 1
-
Confirm presence of satellite data decoder functionalityInspect the firmware or software stack for any satellite data processing module, such as a satellite communication handler, GNSS data parser, or satellite file import featureAffected if The firmware includes a satellite data file decoder or parser component
-
Check if satellite data file input is reachableDetermine whether the device or application can receive or load external satellite data files through user upload, over-the-air updates, or data import featuresAffected if Users or automated processes can supply satellite data files to the system for decoding
-
Review satellite decoder bounds checking implementationExamine the satellite data decoder source code or binary for validation of signature offsets before memory access operations, specifically looking for bounds checking on offset valuesAffected if The decoder lacks rigorous validation of signature offsets, allowing out-of-bounds memory access with malformed files
A user is affected if they are running any of the listed Qualcomm platforms with an active satellite data file decoder that processes external files, as all versions of these products lack proper signature offset validation.
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 rigorous bounds checking and validation of signature offsets before memory access operations in the satellite data decoding routine; reject malformed files with invalid offsets.
- Consultation6.0 h
- Implementation12.0 h
- Testing8.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 $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-47392 — 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-47392 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