dbcve.org
Apq8017 FirmwareOperating system · Qualcomm

CVE-2024-43052

HIGH · 7.8 CVSS v3.1 Published 2024-12-02
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 API calls to NPU with invalid input.

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 exists in the Neural Processing Unit (NPU) API layer when handling improperly formatted or malicious input. The issue allows an attacker to trigger memory corruption via specially crafted API calls to the NPU, potentially leading to code execution or denial of service.

MitigationImplement robust input validation and bounds checking on all NPU API entry points. Apply patches from the hardware/vendor when available.

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
Apq8017 FirmwareOperating system
Affected:all versions
Apq8037 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
Home Hub 100 Platform FirmwareOperating system
Affected:all versions
Msm8108 FirmwareOperating system
Affected:all versions
Msm8209 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 NPU hardware presence
    Check system hardware information for Qualcomm Neural Processing Unit (NPU) or Qualcomm NPU entries in /proc/cpuinfo, device tree, or hardware registers. On Android, check 'getprop' for qualcomm hardware properties or use 'lshw' on Linux-based firmware.
    Affected if The system contains any Qualcomm NPU hardware component such as Apq8017, Apq8037, Fastconnect 6800/6900/7800, Home Hub 100, Msm8108, or Msm8209.
  2. Confirm Qualcomm chip model
    Retrieve the exact Qualcomm chip identifier from /proc/cpuinfo, 'lspci' output, 'dmesg' boot logs, or vendor-specific getprop entries. Match against the affected list: Apq8017, Apq8037, Fastconnect 6800, Fastconnect 6900, Fastconnect 7800, Home Hub 100, Msm8108, Msm8209.
    Affected if The device uses any of the listed Qualcomm chip models or firmware variants.
  3. Check NPU firmware version
    Access NPU firmware version through vendor-specific interfaces. On Qualcomm-based Android devices, query '/sys/class/npu/version' or check vendor debugfs entries under /d/npu/. Review bootloader or baseband firmware logs for NPU firmware revision strings.
    Affected if Any NPU firmware version is installed (all versions of the affected products are vulnerable per the CVE).
  4. Verify NPU API layer is accessible
    Determine if applications or services can make direct API calls to the NPU. Check for NPU driver modules (npu.ko, qcom-npu.ko) loaded in 'lsmod', review /dev/npu* device nodes, or examine if NPU HAL (Hardware Abstraction Layer) service is running.
    Affected if The NPU driver and API interface are loaded and accessible, allowing applications to submit requests to the NPU.
  5. Check for NPU input processing exposure
    Audit which processes or applications have permission to access NPU device nodes or HAL services. Review SELinux policies (on Android) or device permissions for NPU subsystem access. Look for any user-accessible NPU testing or diagnostic interfaces.
    Affected if Any untrusted or third-party application can submit API calls to the NPU interface.

If the environment contains any of the listed Qualcomm NPU hardware components (Apq8017, Apq8037, Fastconnect 6800/6900/7800, Home Hub 100, Msm8108, Msm8209) with the NPU API layer enabled and accessible, the system is affected by this vulnerability since all firmware versions are impacted.

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

Implement robust input validation and bounds checking on all NPU API entry points. Apply patches from the hardware/vendor when available.

Recommended fix Low confidence
  1. Contact Qualcomm directly through their official support channels or partner program to request the firmware update addressing CVE-2024-43052
  2. Provide the CVE identifier and product affected (Apq8017, Apq8037, Fastconnect 6800/6900/7800, Home Hub 100 Platform, Msm8108, or Msm8209) when requesting the update
  3. Apply the Qualcomm-provided firmware update to affected devices following their published firmware update procedures
  4. Verify the NPU firmware has been successfully updated by checking the firmware version or running integrity checks

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

Fix this in Apq8017 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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