CVE-2015-9037
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 · uneditedIn all Qualcomm products with Android releases from CAF using the Linux kernel, a buffer over-read may occur in the processing of a downlink 3G NAS message.
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 · high confidenceA buffer over-read vulnerability exists in Qualcomm's Linux kernel implementation used in Android devices from CAF (Code Aurora Forum). The flaw occurs during processing of downlink 3G NAS (Non-Access Stratum) messages, allowing an attacker to read beyond allocated buffer boundaries. This can potentially expose sensitive memory contents or aid in further exploitation.
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 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/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 if device uses Qualcomm chipset from CAFCheck device specifications or /proc/cpuinfo for Qualcomm processor info; verify if the kernel source is from Code Aurora Forum (CAF) by reviewing build.prop or kernel source if availableAffected if Device uses a Qualcomm chipset with CAF-sourced kernel code for 3G/NAS processing modules
-
Confirm Android version is affectedGo to Settings > About Phone > Android version, or run 'getprop ro.build.version.release' via ADBAffected if Device runs any version of Android (as stated: all versions are affected)
-
Check security patch levelGo to Settings > About Phone > Security patch level, or run 'getprop ro.build.version.security_patch' via ADBAffected if Security patch level is earlier than the month the vendor released the fix for CVE-2015-9037 (patch date varies by OEM)
-
Verify 3G NAS message processing is in useThe vulnerability triggers when processing downlink 3G NAS messages. Check if device operates on 3G networks (WCDMA/HSPA) - monitor network type via *#*#4636#*#* or similar diagnostic toolsAffected if Device uses or switches to 3G/NAS connection processing, as the flaw exists in that specific code path
User is affected if the device uses Qualcomm CAF kernel code for 3G NAS processing and lacks the vendor security patch that addresses CVE-2015-9037, indicated by a security patch level predating the fix release.
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 the vendor-supplied firmware/security patch from the device OEM that includes the Qualcomm fix. Users of affected devices should check for and apply available system updates promptly.
- Consultation4.0 h
- Implementation2.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 $4,928.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-9037 — 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-2015-9037 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