dbcve.org
Aqt1000 FirmwareOperating system · Qualcomm

CVE-2024-45542

HIGH · 7.8 CVSS v3.1 Published 2025-01-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 when IOCTL call is invoked from user-space to write board data to WLAN 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 WLAN driver where an IOCTL call from user-space to write board data lacks proper input validation or bounds checking. The vulnerability allows a local attacker to trigger memory corruption by sending a specially crafted IOCTL request to the WLAN driver.

MitigationApply the vendor-provided patch for the WLAN driver that adds proper input validation and bounds checking in the IOCTL handler. If no patch is available, consider restricting access to the affected IOCTL interface or disabling the WLAN driver until a fix can be applied.

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
Qca1062 FirmwareOperating system
Affected:all versions
Qca1064 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 WLAN hardware present
    Check system for Qualcomm WLAN adapters. On Linux, run 'lspci | grep -i network' or 'lspci | grep -i wireless' for PCIe cards, or 'lsusb' for USB adapters. Look for Qualcomm Aqt1000, Fastconnect 6200/6700/6800/6900/7800, or QCA1062/1064 in the device listing.
    Affected if Any of the listed Qualcomm chip models (Aqt1000, Fastconnect 6200/6700/6800/6900/7800, Qca1062, Qca1064) are present in the system
  2. Check WLAN firmware version
    Retrieve the firmware version loaded for the Qualcomm WLAN chip. On Linux, check /sys/class/net/*/device/firmware_version or use 'iw list' for wireless devices. For Android, check 'getprop' or settings. The version string typically appears in the firmware revision or version output.
    Affected if The installed firmware version matches any of the affected chip families (Aqt1000, Fastconnect series, Qca1062/1064) - all versions of these chips are affected
  3. Verify driver IOCTL interface accessibility
    Confirm the WLAN driver is loaded and the IOCTL interface is accessible. On Linux, check if the wireless driver (ath11k, ath12k, qca_* driver) is loaded via 'lsmod | grep -i ath' or 'lsmod | grep -i qca'. Also verify /dev/wireless or similar device nodes exist.
    Affected if The Qualcomm WLAN driver is loaded and active, exposing the IOCTL interface to user-space processes
  4. Check for board data IOCTL usage
    Examine if applications or scripts interact with WLAN driver IOCTLs for board data operations. Look for ioctl calls with SIOCDEVPRIVATE or similar commands in any custom or third-party wireless management tools. Review any scripts that directly call IOCTLs on the WLAN interface.
    Affected if The system runs software that makes IOCTL calls to the WLAN driver for board data operations, enabling the attack vector

A system is affected if it contains any of the listed Qualcomm WLAN chips (Aqt1000, Fastconnect 6200/6700/6800/6900/7800, Qca1062, Qca1064) with an active driver that exposes the IOCTL interface to user-space, as all firmware versions of these chips lack proper input validation in the board data IOCTL handler.

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 the vendor-provided patch for the WLAN driver that adds proper input validation and bounds checking in the IOCTL handler. If no patch is available, consider restricting access to the affected IOCTL interface or disabling the WLAN driver until a fix can be applied.

Fix this in Aqt1000 Firmware Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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