dbcve.org
Fastconnect 6800 FirmwareOperating system · Qualcomm

CVE-2025-27037

HIGH · 7.8 CVSS v3.1 Published 2025-09-24
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 config_dev IOCTL when camera kernel driver drops its reference to CPU 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 kernel driver's handling of the config_dev IOCTL. When the camera kernel driver drops its reference to CPU buffers during IOCTL processing, it can lead to use-after-free or similar memory corruption issues. This kernel-level flaw could allow local attackers to cause denial of service or potentially escalate privileges.

MitigationApply vendor-provided kernel driver patches for the camera subsystem. Ensure proper synchronization and reference counting mechanisms are implemented when handling buffer references in IOCTL 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 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 Qualcomm Fastconnect WiFi adapters
    Run 'lspci' or 'lsusb' to list network and wireless adapters. Look for Qualcomm Atheros Fastconnect 6800, 6900, or 7800 devices. On Linux, 'lspci -v | grep -i qualcomm' or 'rfkill list' may reveal these devices.
    Affected if A Qualcomm Fastconnect 6800, 6900, or 7800 wireless adapter is present in the system
  2. Identify Qualcomm camera or imaging devices
    Check for Qualcomm camera subsystems using 'ls /dev/video*', 'v4l2-ctl --list-devices', or checking kernel logs for Qualcomm camera driver modules. Look for Qam8295p or similar Qualcomm imaging firmware devices.
    Affected if A Qualcomm Qam8295p or other listed Qualcomm camera/imaging device is present
  3. Check firmware versions of Qualcomm WiFi devices
    Query the installed firmware version on identified Qualcomm wireless devices. On Linux, check /lib/firmware/ath11k or similar Qualcomm firmware directories, or use 'iw list' or 'ethtool -i <interface>' to retrieve firmware version information.
    Affected if The firmware version of any Qualcomm Fastconnect device cannot be determined or is older than vendor patches (all versions are affected)
  4. Check for config_dev IOCTL exposure
    Verify if the camera driver config_dev IOCTL interface is accessible. This typically requires checking /dev/video* devices and examining driver support. Use 'v4l2-ctl --all' to query device capabilities, or check kernel module parameters for camera driver configurations.
    Affected if The system has camera devices with Qualcomm-based drivers and the config_dev IOCTL interface is exposed to user space

A system is affected if it contains any Qualcomm Fastconnect WiFi adapters (6800/6900/7800) or Qualcomm camera/imaging devices (Qam8295p, Qca6391/6426/6436/6574au) with accessible camera driver IOCTL interfaces, as all firmware versions of these products contain the vulnerability.

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 kernel driver patches for the camera subsystem. Ensure proper synchronization and reference counting mechanisms are implemented when handling buffer references in IOCTL handlers.

Fix this in Fastconnect 6800 Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation24.0 h
  • Testing16.0 h
  • Review / QA8.0 h
56.0 hours of engineering $9,760
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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