CVE-2024-33058
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 · uneditedMemory corruption while assigning memory from the source DDR memory(HLOS) to ADSP.
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 confidenceMemory corruption vulnerability in Qualcomm components during assignment of DDR memory from HLOS (High-Level Operating System) to ADSP (Application Digital Signal Processor). The flaw allows corruption of memory boundaries when the HLOS allocates and transfers memory regions to the ADSP subsystem.
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 dataall versionsall versionsall versionsall versionsall versionsall versionsall versionsall versionsCVSS 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
- High
- Privileges
- High
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:C/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Qualcomm ADSP components in the systemCheck system firmware, device tree, or boot logs for presence of Aqt1000, Ar8035, Fastconnect 6200/6700/6800/6900/7800, or Qam8255p firmware modules. On Linux, inspect /sys/firmware/devicetree or review boot logs (dmesg) for these component identifiers.Affected if Any of the listed Qualcomm firmware components (Aqt1000, Ar8035, Fastconnect series, Qam8255p) are present in the system
-
Verify ADSP subsystem is activeCheck if the Application Digital Signal Processor (ADSP) is enabled and running. On Android devices, examine /dev/adsp* or /dsp/ directories. On embedded systems, review kernel modules (lsmod) for adsp-related modules and check process lists for ADSP-related services.Affected if ADSP subsystem is loaded and operational on the device
-
Confirm HLOS-to-ADSP memory assignment is in useReview system configuration for DDR memory allocation policies between HLOS and ADSP. Check debug interfaces, firmware logs, or memory management configuration files that control memory transfer from the High-Level Operating System to the ADSP subsystem.Affected if HLOS-to-ADSP memory assignment/transfer functionality is configured or active
-
Check firmware version of affected componentsQuery firmware version of the identified Qualcomm component. On Linux systems, this may be available via debugfs, vendor-specific tools, or by reading firmware version from /sys/class/.../version. Compare against the affected product list - note all versions of these products are affected.Affected if The device runs any firmware version of the listed Qualcomm products (all versions are affected)
A device is affected if it contains any of the listed Qualcomm firmware components (Aqt1000, Ar8035, Fastconnect series, Qam8255p) with an active ADSP subsystem that performs HLOS-to-ADSP memory assignment.
Generated from the published advisory. Verify against your own configuration.
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 dataApply Qualcomm firmware/security updates provided by device OEMs. If no update is available, restrict ADSP functionality or minimize exposure of affected devices to untrusted inputs.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,192.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-33058 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-33058 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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