CVE-2018-5907
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 · uneditedPossible buffer overflow in msm_adsp_stream_callback_put due to lack of input validation of user-provided data that leads to integer overflow in all Android releases(Android for MSM, Firefox OS for MSM, QRD Android) from CAF using the Linux kernel.
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 confidenceBuffer overflow vulnerability in msm_adsp_stream_callback_put function in Qualcomm MSM audio DSP driver due to integer overflow caused by insufficient input validation on user-controlled data, potentially allowing local privilege escalation or denial of service.
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<= 8.1CVSS 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.0/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 checksWork through these to decide whether this CVE applies to you.
-
Check Android versionGo to Settings > About Phone > Android version, or run 'getprop ro.build.version.release' via ADBAffected if Android version is 8.1 or lower (8.0, 7.x, 6.x, etc.)
-
Verify device uses Qualcomm chipsetRun 'getprop ro.hardware' or 'getprop ro.chipset' via ADB to identify the chipset manufacturerAffected if Device uses a Qualcomm MSM (Mobile Station Modem) chipset - common identifiers include 'msm' in the hardware property
-
Check if msm_adsp audio driver is presentRun 'ls /dev/snd/' or check kernel modules with 'lsmod | grep msm_adsp' via ADB shell, or inspect /proc/modulesAffected if The msm_adsp or msm_audio_dsp module is loaded or the /dev/audio* devices exist from this driver
-
Inspect kernel configuration for audio DSP supportCheck /proc/config.gz (if available) or boot.img kernel config for CONFIG_MSM_ADSP or CONFIG_MSM_AUDIO_DSP optionsAffected if Audio DSP driver support is compiled into the kernel (not disabled)
-
Identify kernel patch levelRun 'getprop ro.build.version.security_patch' via ADB to get the Android security patch dateAffected if Security patch level is earlier than the March 2018 security bulletin for this specific CVE
Device is likely affected if running Android 8.1 or earlier on Qualcomm MSM hardware with the msm_adsp audio DSP driver enabled, and the kernel security patch predates the CVE fix.
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 security patches from CAF/Android security bulletins that add proper input validation in the msm_adsp_stream_callback_put function; kernel-level update required.
- Consultation6.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
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 locallyCheck whether your project pulls in CVE-2018-5907 — 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-2018-5907 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