dbcve.org
Aqt1000 FirmwareOperating system · Qualcomm

CVE-2025-21470

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 image encoding, when configuration is NULL in IOCTL parameter.

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

Memory corruption vulnerability in image encoding processing that occurs when a NULL configuration pointer is passed in an IOCTL parameter. This suggests insufficient validation of the configuration parameter before use in memory operations, likely leading to NULL pointer dereference and subsequent memory corruption.

MitigationApply available vendor security updates for affected Windows systems. Implement input validation to ensure configuration parameters are not NULL before dereferencing 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
Aqt1000 FirmwareOperating system
Affected:all versions
Fastconnect 6200 FirmwareOperating system
Affected:all versions
Fastconnect 6700 FirmwareOperating system
Affected:all versions
Fastconnect 6800 FirmwareOperating system
Affected:all versions
Fastconnect 6900 FirmwareOperating system
Affected:all versions
Fastconnect 7800 FirmwareOperating system
Affected:all versions
Qca6391 FirmwareOperating system
Affected:all versions
Qca6420 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 present
    Run 'lspci' or check device manager for Qualcomm network adapters matching Aqt1000, Fastconnect 6200/6700/6800/6900/7800, Qca6391, or Qca6420. On Windows, use 'devcon listclass net' or check network adapter properties.
    Affected if The system has any of the listed Qualcomm wireless chips installed.
  2. Retrieve installed firmware version
    Use vendor tools (e.g., 'qcusbnetdiag' for Qualcomm adapters) or check firmware version through the wireless adapter driver properties. On Linux, check '/sys/class/net/*/device/firmware_version' or use 'ethtool -i <interface>'.
    Affected if The firmware version returned falls within the affected product list (all versions of these firmware products are vulnerable).
  3. Determine if image encoding IOCTL interface is accessible
    Monitor IOCTL calls related to image encoding (look for IOCTL codes in the 0x8xxx range associated with imaging or encoding functions). Use tools like 'iotrace' or 'sysinternals' on Windows to capture driver IOCTL requests. On Linux, trace with 'strace' or 'ftrace' on the wireless driver.
    Affected if The system's wireless driver exposes an IOCTL interface for image encoding processing that accepts configuration parameters.
  4. Verify NULL pointer handling in driver
    If you have driver debugging capabilities, test passing NULL as the configuration pointer in an image encoding IOCTL request and observe if a NULL pointer dereference or memory corruption occurs. Otherwise, check driver changelog or vendor security advisory for mention of CVE-2025-21470.
    Affected if The driver does not validate the configuration pointer before use in memory operations, allowing NULL pointer dereference.

A system is affected if it contains any of the listed Qualcomm wireless firmware products (Aqt1000, Fastconnect 6200/6700/6800/6900/7800, Qca6391, Qca6420) and the image encoding IOCTL interface is exposed and used without proper NULL pointer validation.

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 available vendor security updates for affected Windows systems. Implement input validation to ensure configuration parameters are not NULL before dereferencing in IOCTL handlers.

Fix this in Aqt1000 Firmware Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA6.0 h
34.0 hours of engineering $5,940
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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