dbcve.org
Qam8255p FirmwareOperating system · Qualcomm

CVE-2025-47393

HIGH · 7.8 CVSS v3.1 Published 2026-01-07
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 accessing resources in kernel driver.

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 a kernel-mode driver that occurs when accessing resources. The high CVSS score (7.8) suggests the issue allows local or adjacent attackers to corrupt kernel memory, potentially leading to privilege escalation or system instability. The generic description indicates the vulnerability is in resource handling code within the driver.

MitigationApply any available vendor patches for the affected kernel driver. If no patch exists, consider disabling or replacing the vulnerable driver, implementing kernel-level access controls, and ensuring the principle of least privilege for driver resource allocation.

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
Qam8255p FirmwareOperating system
Affected:all versions
Qam8650p FirmwareOperating system
Affected:all versions
Qam8775p FirmwareOperating system
Affected:all versions
Qamsrv1h FirmwareOperating system
Affected:all versions
Qamsrv1m FirmwareOperating system
Affected:all versions
Qca6595 FirmwareOperating system
Affected:all versions
Qca6698aq FirmwareOperating system
Affected:all versions
Qca6797aq 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 device model and Qualcomm chipset
    Check the device documentation, system information, or boot logs to determine if the hardware uses any of the following Qualcomm chips: Qam8255p, Qam8650p, Qam8775p, Qamsrv1h, Qamsrv1m, Qca6595, Qca6698aq, or Qca6797aq. This can often be found via 'lspci', 'lsmem', or vendor-specific diagnostic tools.
    Affected if The device uses any of the listed Qualcomm firmware chipsets
  2. Check installed firmware version
    Retrieve the firmware version from the device or system. For embedded devices, this may be accessible via: cat /proc/version, dmesg, vendor-specific tools, or bootloader information. Compare the version string against the affected product list.
    Affected if The device firmware matches any of the affected Qualcomm products (all versions of Qam8255p, Qam8650p, Qam8775p, Qamsrv1h, Qamsrv1m, Qca6595, Qca6698aq, Qca6797aq)
  3. Verify kernel driver is loaded
    Check if the vulnerable kernel-mode driver is active. Use commands like 'lsmod', 'cat /proc/modules', or system driver logs to identify if the Qualcomm wireless or connectivity driver modules are loaded and running.
    Affected if The Qualcomm kernel-mode driver for the affected chipset is loaded and actively handling resources
  4. Inspect kernel resource handling
    Review kernel logs (dmesg, journalctl) and any available driver debug logs for memory corruption indicators, resource access errors, or unexpected driver behavior that may suggest the vulnerability is being triggered.
    Affected if Kernel logs show memory corruption, resource access violations, or unexpected driver crashes related to the Qualcomm driver

A device is affected if it uses any of the listed Qualcomm chipsets (Qam8255p, Qam8650p, Qam8775p, Qamsrv1h, Qamsrv1m, Qca6595, Qca6698aq, Qca6797aq) with the vulnerable kernel-mode driver loaded, since all versions of these firmwares contain the 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

Apply any available vendor patches for the affected kernel driver. If no patch exists, consider disabling or replacing the vulnerable driver, implementing kernel-level access controls, and ensuring the principle of least privilege for driver resource allocation.

Fix this in Qam8255p Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA4.0 h
36.0 hours of engineering $6,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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