dbcve.org
Fastconnect 6900 FirmwareOperating system · Qualcomm

CVE-2025-47358

HIGH · 7.8 CVSS v3.1 Published 2026-02-02
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 user space address is modified and passed to mem_free API, causing kernel memory to be freed inadvertently.

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 where a user-space address can be modified (likely through a race condition or manipulation) before being passed to the mem_free API. This causes the kernel to inadvertently free kernel memory instead of the intended user-space memory, leading to potential use-after-free conditions and system instability.

MitigationImplement strict validation of pointer addresses before passing to mem_free, ensuring pointers originate from the expected memory space and cannot be manipulated to reference kernel memory regions.

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
Qcc2072 FirmwareOperating system
Affected:all versions
Sc8380xp FirmwareOperating system
Affected:all versions
Snapdragon 8cx Gen 3 Compute Platform FirmwareOperating system
Affected:all versions
Wcd9378c FirmwareOperating system
Affected:all versions
Wcd9380 FirmwareOperating system
Affected:all versions
Wcd9385 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 Qualcomm Fastconnect WiFi firmware presence
    Check system for Qualcomm Fastconnect 6900 or 7800 WiFi firmware by examining firmware class sysfs entries, dmesg logs for firmware loading messages, or using tools like 'iw list' to query wireless device firmware version
    Affected if The system has Fastconnect 6900 or Fastconnect 7800 firmware loaded - all versions are affected
  2. Identify Qualcomm WCD audio codec firmware
    Examine audio codec firmware by checking ALSA sound card information, looking for WCD9378c, WCD9380, or WCD9385 in system logs (dmesg, journalctl), or querying the audio subsystem for codec firmware versions
    Affected if The system uses WCD9378c, WCD9380, or WCD9385 audio codec firmware - all versions are affected
  3. Identify Qualcomm Qcc2072 Bluetooth audio firmware
    Check for Qcc2072 Bluetooth audio device presence using Bluetooth management tools (bluetoothctl, hciconfig), examining bluez firmware loading logs, or checking /sys/class/bluetooth for device firmware information
    Affected if The system has Qcc2072 Bluetooth audio firmware loaded - all versions are affected
  4. Identify Snapdragon 8cx Gen 3 Compute Platform firmware
    On systems with Snapdragon 8cx Gen 3 (Windows on ARM devices, some laptops), check firmware versions through system firmware/UEFI interfaces, or examine ACPI tables for platform firmware version information
    Affected if The device runs on Snapdragon 8cx Gen 3 Compute Platform firmware - all versions are affected
  5. Identify Sc8380xp firmware presence
    Check for Sc8380xp component firmware through platform-specific diagnostics, system firmware logs, or hardware enumeration tools that report embedded controller or platform controller firmware versions
    Affected if The system has Sc8380xp firmware installed - all versions are affected

If any of these Qualcomm firmware components (Fastconnect 6900/7800, WCD9378c/WCD9380/WCD9385, Qcc2072, Snapdragon 8cx Gen 3, or Sc8380xp) are present in the environment, the system is affected since all versions of each are vulnerable.

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 strict validation of pointer addresses before passing to mem_free, ensuring pointers originate from the expected memory space and cannot be manipulated to reference kernel memory regions.

Fix this in Fastconnect 6900 Firmware Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-47358 — 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-47358 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