dbcve.org
Fastconnect 6900 FirmwareOperating system · Qualcomm

CVE-2025-21462

HIGH · 7.8 CVSS v3.1 Published 2025-05-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 an IOCTL request, when buffer significantly exceeds the command argument limit.

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 IOCTL request handling where inadequate boundary validation allows a buffer to significantly exceed the command argument limit, leading to memory corruption. This could allow a local attacker to escalate privileges or cause a denial of service.

MitigationApply vendor security updates for the affected Windows kernel/driver component. Until patched, restrict local access to privileged users only to reduce attack surface.

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
Sa4150p FirmwareOperating system
Affected:all versions
Sa4155p FirmwareOperating system
Affected:all versions
Sa6155p FirmwareOperating system
Affected:all versions
Sa8155p FirmwareOperating system
Affected:all versions
Sa8195p FirmwareOperating system
Affected:all versions
Sc8380xp 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 wireless hardware in the system
    Open Device Manager (Windows) or run 'lspci | grep -i network' (Linux) to list network adapters. Look for Qualcomm Fastconnect or Snapdragon product names such as Fastconnect 6900, Fastconnect 7800, Sa4150p, Sa4155p, Sa6155p, Sa8155p, Sa8195p, or Sc8380xp in the adapter description or hardware IDs.
    Affected if Any of the listed Qualcomm wireless products (Fastconnect 6900/7800 or any Sa/Snapdragon model in the list) are present in the system.
  2. Verify the IOCTL interface is loaded
    Check if the Qualcomm wireless driver is loaded and running. On Windows, run 'sc query QWAVE' or check Device Manager for the Qualcomm wireless adapter status. On Linux, check 'lsmod' for loaded wireless modules or check 'rfkill list' output for Qualcomm devices.
    Affected if The Qualcomm wireless adapter driver is loaded and active, exposing the vulnerable IOCTL handler.
  3. Check for exposed IOCTL device interface
    On Windows, enumerate device interfaces related to Qualcomm wireless: open an elevated command prompt and run 'powershell Get-PnpDevice -Class Net | Where-Object {$_.FriendlyName -match "Qualcomm"}' to list active Qualcomm network devices. Check for associated device paths under \\Device\\ or in the registry under HKLM\SYSTEM\CurrentControlSet\Services.
    Affected if The system has an active Qualcomm wireless device with an exposed IOCTL interface that accepts user-mode requests.

A system is affected if it contains any Qualcomm Fastconnect 6900/7800 or Snapdragon (Sa/Sc series) wireless hardware with the driver loaded, since all firmware versions of these products are vulnerable to the memory corruption flaw in IOCTL handling.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor security updates for the affected Windows kernel/driver component. Until patched, restrict local access to privileged users only to reduce attack surface.

Recommended fix Moderate confidence
  1. Identify the specific Qualcomm component (Fastconnect or Snapdragon Automotive) in your product by checking the firmware version or BOM
  2. Contact Qualcomm directly through their secure reporting channel or your Qualcomm representative to request the firmware patch for CVE-2025-21462
  3. Contact your device/OEM manufacturer if you are not Qualcomm directly, as they will need to integrate the Qualcomm patch into their firmware release
  4. Apply the vendor-provided firmware update that addresses the out-of-bounds write vulnerability in the IOCTL request handling
  5. Verify the patch was applied successfully by confirming the updated firmware version
Caveat Firmware updates may require system downtime and should be tested in a staging environment before production deployment; contact OEM for specific update procedures

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Fastconnect 6900 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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