CVE-2015-9066
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 in an Inter-RAT procedure.
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 the Inter-RAT (Radio Access Technology) procedure within the Linux kernel components of Qualcomm chipsets used in Android devices. This critical flaw allows potential remote code execution in the wireless communication subsystem, affecting all Qualcomm-based Android releases from Code Aurora Forum.
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.
-
Confirm the device uses a Qualcomm chipsetCheck the processor/chipset information via 'cat /proc/cpuinfo' or 'getprop ro.hardware' or 'getprop ro.chipset' in Android shellAffected if The device uses a non-Qualcomm chipset (the vulnerability only affects Qualcomm-based Android devices)
-
Check the kernel versionRun 'uname -r' or 'cat /proc/version' to obtain the kernel version stringAffected if The kernel version falls within the unpatched version range for this CVE (kernel versions prior to the Qualcomm patch release)
-
Verify the Inter-RAT module statusCheck for the presence and configuration of the Inter-RAT radio module in the kernel config: 'cat /boot/config-$(uname -r) | grep CONFIG_QRTR' or check /proc/config.gz if availableAffected if The Inter-RAT/QRTR module is present and loaded on a Qualcomm device (this is the vulnerable component)
-
Check for CVE-2015-9066 patch presenceSearch for CVE-2015-9066 in the Android security patch level: 'getprop ro.build.version.security_patch' or check the kernel symbol table for Inter-RAT related fixesAffected if The security patch level is earlier than the month this vulnerability was patched by Qualcomm (the patch was released in 2015)
A defender is affected if they are running an unpatched Qualcomm-based Android device with a kernel version prior to the CVE-2015-9066 patch release and the Inter-RAT subsystem is enabled.
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-specific patches from Qualcomm and downstream Android security updates; given the kernel-level nature of this vulnerability, OEM/ODM firmware updates are required rather than application-level fixes.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.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 $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-9066 — 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-9066 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