dbcve.org
Fastconnect 6800 FirmwareOperating system · Qualcomm

CVE-2025-21474

HIGH · 7.8 CVSS v3.1 Published 2025-08-06
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 while processing commands from A2dp sink command queue.

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

This is a memory corruption vulnerability in the A2DP (Advanced Audio Distribution Profile) sink component, specifically occurring when processing commands from the command queue. The flaw allows memory corruption during Bluetooth audio command handling, likely due to improper bounds checking, validation, or memory management when dequeuing and processing A2DP sink commands.

MitigationApply vendor-provided patches for the Bluetooth stack implementation. If no patch is available, disable A2DP sink functionality as a workaround until a fix can be deployed.

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 6800 FirmwareOperating system
Affected:all versions
Fastconnect 6900 FirmwareOperating system
Affected:all versions
Fastconnect 7800 FirmwareOperating system
Affected:all versions
Qam8295p FirmwareOperating system
Affected:all versions
Qca6391 FirmwareOperating system
Affected:all versions
Qca6426 FirmwareOperating system
Affected:all versions
Qca6436 FirmwareOperating system
Affected:all versions
Qca6574au 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 Bluetooth firmware version
    Use the system Bluetooth management interface (e.g., 'btmgmt -i <adapter> info' or 'hciconfig -a') to retrieve firmware version information. Alternatively, check '/sys/class/bluetooth/hci*/firmware_dump' or vendor-specific diagnostic tools provided by the OEM.
    Affected if The firmware version matches any of the affected Qualcomm variants: Fastconnect 6800/6900/7800, Qam8295p, Qca6391, Qca6426, Qca6436, or Qca6574au.
  2. Confirm the Bluetooth chipset vendor
    Execute 'lspci | grep -i bluetooth' (for PCIe cards) or 'lsusb' (for USB adapters) to identify the hardware vendor and model. Cross-reference with Qualcomm product documentation to verify the chipset.
    Affected if The system uses a Qualcomm Bluetooth chipset from the affected product list.
  3. Verify if A2DP sink is enabled
    Check the Bluetooth profile configuration: on Linux, use 'bluetoothctl info' or check /etc/bluetooth/audio.conf. On Android, inspect Bluetooth stack settings. Look for 'A2DP Sink' or 'AdvancedAudioSink' in enabled profiles.
    Affected if A2DP sink profile is actively enabled or connected to any Bluetooth audio source.
  4. Inspect Bluetooth command queue processing
    Enable Bluetooth debug logging (e.g., 'btmon' or vendor diagnostic tools) and monitor for errors related to 'A2DP' and 'command queue' processing. Check system logs (journalctl -b | grep -i bluetooth) for crash or memory corruption indicators.
    Affected if Any A2DP-related errors, queue processing failures, or memory corruption events appear in logs after audio activity.
  5. Check for available firmware patches
    Consult the OEM or Qualcomm product security advisories to determine if a firmware update addressing CVE-2025-21474 has been released for your specific chipset model.
    Affected if No vendor patch has been applied and the system uses an affected firmware version with A2DP sink enabled.

A system is affected if it uses any of the listed Qualcomm Bluetooth firmware variants, has A2DP sink functionality enabled, and lacks the corresponding vendor security patch.

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

Apply vendor-provided patches for the Bluetooth stack implementation. If no patch is available, disable A2DP sink functionality as a workaround until a fix can be deployed.

Fix this in Fastconnect 6800 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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