CVE-2015-9041
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 overflow vulnerability exists when performing WCDMA radio tuning.
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 buffer overflow vulnerability exists in Qualcomm Android products using the Linux kernel from CAF (Code Aurora Forum). The overflow occurs during WCDMA (3G) radio tuning operations, potentially allowing remote code execution or denial of service via specially crafted radio parameters.
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.
-
Check for Qualcomm baseband processorRun 'getprop ro.hardware' or 'getprop ro.board.platform' in ADB shell, or check Settings > About Phone > HardwareAffected if The output shows Qualcomm/Snapdragon identifiers - this vulnerability only affects Qualcomm-based Android devices
-
Verify WCDMA/3G capability is presentCheck if the device supports 3G/WCDMA in Settings > Mobile Networks > Network Mode, or inspect radio band capabilities via 'getprop' commands like 'getprop gsm.network.type'Affected if WCDMA/3G radio capability is enabled or available on the device - the overflow occurs specifically during WCDMA tuning operations
-
Confirm Android version in useRun 'getprop ro.build.version.release' or check Settings > About Phone > Android versionAffected if Any Android version is installed - the CVE states all versions are affected
-
Check kernel version for patch statusRun 'uname -a' or 'getprop ro.kernel.version' in ADB shell to identify the CAF (Code Aurora Forum) kernel versionAffected if Running an unpatched CAF kernel version from 2015 or earlier without the CVE-2015-9041 security fix
Device is affected if it uses a Qualcomm chipset with active WCDMA/3G capability and is running an unpatched Android/CAF kernel build.
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-supplied firmware/security updates from Qualcomm or OEM partners. Until patched, limit exposure by avoiding untrusted networks and third-party radio applications.
- Consultation12.0 h
- Implementation4.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 $11,136.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-9041 — 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-9041 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