dbcve.org
Fastconnect 6900 FirmwareOperating system · Qualcomm

CVE-2025-47405

HIGH · 7.8 CVSS v3.1 Published 2026-05-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
Zero-click

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 · unedited
Memory corruption when processing camera sensor input/output control codes with invalid output buffers.

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 confidence

A memory corruption vulnerability exists in the camera sensor input/output control code processing path. When handling control codes with invalid output buffers (e.g., undersized or NULL buffers), the code fails to properly validate buffer parameters before performing memory operations, leading to heap or stack corruption that could allow privilege escalation.

MitigationImplement robust buffer validation in the camera sensor I/O control code path, ensuring output buffer size and validity are verified before any memory copy operations; consider adding bounds checking and defensive programming around all buffer parameters passed to sensor control handlers.

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 data
Fastconnect 6900 FirmwareOperating system
Affected:all versions
Fastconnect 7800 FirmwareOperating system
Affected:all versions
Iqx5121 FirmwareOperating system
Affected:all versions
Iqx7181 FirmwareOperating system
Affected:all versions
Qca0000 FirmwareOperating system
Affected:all versions
Sc8380xp FirmwareOperating system
Affected:all versions
Sd865 5g FirmwareOperating system
Affected:all versions
Snapdragon Xr2 5g FirmwareOperating system
Affected:all versions

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the chipset model
    Check the device or system information to determine if the chipset matches any of the affected Qualcomm models: Fastconnect 6900, Fastconnect 7800, Iqx5121, Iqx7181, Qca0000, Sc8380xp, Sd865 5g, or Snapdragon Xr2 5g
    Affected if The device uses any of the listed Qualcomm chipsets
  2. Determine the firmware version
    Query the firmware version of the applicable Qualcomm component (camera sensor driver, Fastconnect, or baseband firmware) using manufacturer-provided tools, /proc filesystem, or system logs
    Affected if The firmware version is present and the chipset matches an affected model (all versions of these chipsets are affected)
  3. Verify camera sensor interface is active
    Check if the camera sensor I/O control interface is accessible or loaded by examining running processes, kernel modules (such as camera sensor drivers), or system configuration files related to camera or imaging subsystems
    Affected if Camera sensor I/O control functionality is present and operational on the device
  4. Check for buffer validation in sensor control path
    Examine any available debug logs, system logs, or diagnostic outputs related to camera sensor control code for evidence of buffer handling, especially control code operations with output buffers. If source code or symbol information is available, review the sensor control handler functions for buffer validation logic
    Affected if Buffer validation is missing or insufficient in the sensor control code path (this requires access to firmware symbols, debug builds, or vendor diagnostic tools)
  5. Review camera driver configuration
    Inspect camera driver or sensor module configuration files and parameters to determine if control code operations with external buffers are enabled or reachable
    Affected if Camera sensor control code paths that handle external output buffers are exposed or enabled in the configuration

A user is affected if their device uses any of the listed Qualcomm chipset models and the camera sensor I/O control feature is operational, since all versions of these firmwares contain the buffer validation flaw.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement robust buffer validation in the camera sensor I/O control code path, ensuring output buffer size and validity are verified before any memory copy operations; consider adding bounds checking and defensive programming around all buffer parameters passed to sensor control handlers.

Fix this in Fastconnect 6900 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,880
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,808.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-47405 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-47405 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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