CVE-2024-49848
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 processing multiple IOCTL calls from HLOS to DSP.
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 confidenceA memory corruption vulnerability exists in the DSP subsystem where processing multiple IOCTL calls from the HLOS (High-Level Operating System) leads to memory corruption, likely due to improper handling of state or buffers across sequential IOCTL requests.
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
- Low
- Privileges
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Qualcomm DSP firmwareCheck system firmware or bootloader logs for loaded Qualcomm DSP components (look for strings like 'Qam8255p', 'Qam8295p', 'Qam8620p', 'Qam8650p', 'Qam8775p', 'Qamsrv1h', 'Qamsrv1m', 'Qca6174a'). On Linux, check /vendor/firmware/ or /lib/firmware/ for these firmware files.Affected if Any of the listed firmware files (Qam8255p, Qam8295p, Qam8620p, Qam8650p, Qam8775p, Qamsrv1h, Qamsrv1m, Qca6174a) are present on the system
-
Verify DSP IOCTL interface accessibilityCheck if the DSP subsystem device node exists and is accessible. On Android/Linux systems, look for /dev/dsp, /dev/msm_dsp, /dev/audio_dsp, or similar DSP device files. Use 'ls -la /dev/*dsp*' to enumerate.Affected if The DSP device interface is exposed and accessible to untrusted applications (world-writable or group-accessible permissions)
-
Confirm DSP driver is loadedCheck kernel modules for DSP-related drivers. On Linux, run 'lsmod | grep -i dsp' or check /proc/modules. Look for modules like 'q6dsp', 'msm-dsp', 'audio-dsp', or similar Qualcomm DSP drivers.Affected if A Qualcomm DSP driver module is loaded and the DSP hardware is active
-
Check for DSP IOCTL usageAudit application access to DSP device nodes using audit rules or strace. Look for ioctl system calls targeting /dev/dsp* or /dev/msm_dsp* device files.Affected if Multiple IOCTL calls to the DSP device are being made by applications, particularly sequential requests that may trigger the memory corruption
If any Qualcomm DSP firmware from the affected list is present and the DSP IOCTL interface is accessible, the system is vulnerable to memory corruption via sequential IOCTL requests.
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 vendor-provided firmware updates for the DSP subsystem and restrict access to the IOCTL interface to trusted processes only.
- Consultation8.0 h
- Implementation24.0 h
- Testing16.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $15,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-49848 — 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-49848 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