CVE-2025-47389
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 buffer copy operation fails due to integer overflow during attestation report generation.
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 memory corruption vulnerability where an integer overflow causes a buffer copy operation to fail during attestation report generation. The overflow allows an incorrect size value to be used in the copy operation, leading to potential memory corruption.
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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/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 firmware component in useExamine system information, device firmware manifest, or modem firmware identification to determine if the system uses any of the affected firmware: Ar8035, Cologne, Csra6620, Csra6640, Fastconnect 6200, Snapdragon X35 5G Modem RF, Snapdragon X53 5G Modem RF, or Snapdragon X55 5G Modem RFAffected if The system implements any of the listed Qualcomm firmware components
-
Verify attestation report generation is enabledCheck configuration settings, system logs, or attestation service status to determine if the attestation report generation feature is active on the deviceAffected if Attestation report generation functionality is enabled and being used
-
Check for firmware version informationQuery the modem or wireless firmware subsystem for its version string using AT commands, firmware debug interfaces, or system firmware retrieval toolsAffected if A Qualcomm firmware version is returned from any of the affected product families (all versions are affected)
-
Review attestation-related memory operationsMonitor or analyze memory allocation and copy operations during attestation report generation for signs of unexpected behavior or corruption patternsAffected if Attestation report generation code path is exercised on the device
The environment is affected if it uses any of the listed Qualcomm firmware components (Ar8035, Cologne, Csra6620, Csra6640, Fastconnect 6200, Snapdragon X35/X53/X55 5G Modem RF) and has attestation report generation enabled, as all versions of these firmwares contain the integer overflow vulnerability in the attestation code path.
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 bounds checking and integer overflow validation on all size calculations before buffer copy operations in the attestation report generation code path. Use safe integer arithmetic and validate input ranges.
- Consultation3.0 h
- Implementation6.0 h
- Testing5.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 $4,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-47389 — 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-47389 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