CVE-2015-9051
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 vulnerability exists in LTE where an assertion can be reached due to an improper bound on a length in a System Information 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 · moderate confidenceA vulnerability in Qualcomm LTE baseband firmware allows an attacker to trigger an assertion failure by sending a specially crafted System Information message with an improperly bounded length field. This can cause a denial of service on affected Android devices using Qualcomm chipsets with Linux kernel-based CAF releases.
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 Qualcomm chipset usageRun 'getprop ro.product.board' or check /proc/cpuinfo for 'Qualcomm' identifier, or use 'getprop gsm.version.baseband' to see baseband firmware stringAffected if Device does not show Qualcomm-related identifiers in baseband or processor information - if not Qualcomm, not affected by this specific baseband vulnerability
-
Check baseband firmware versionExecute 'getprop gsm.version.baseband' or 'getprop ro.baseband' to retrieve the installed LTE baseband firmware version stringAffected if Unable to retrieve baseband version information or version string indicates non-Qualcomm baseband (e.g., MediaTek, Intel, Samsung) - the vulnerability only affects Qualcomm chipsets
-
Verify LTE connectivity capabilityCheck if device has LTE capability by examining 'getprop ro.telephony.default_network' or checking /sys/class/net/* for LTE interfacesAffected if Device has no LTE capability or baseband does not support LTE - the flaw is in LTE baseband firmware specifically
-
Check security patch levelLook at 'getprop ro.build.version.security_patch' or Settings > About Phone > Android security patch level to see last applied updateAffected if Security patch level is older than 2015-03-01 or shows no patches applied - the advisory indicates patches are needed from Qualcomm/carriers to mitigate this flaw
Device is affected if it uses a Qualcomm LTE baseband chipset (check via baseband firmware string) and has not received baseband/firmware security updates addressing this specific vulnerability.
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 patches from Qualcomm and/or your mobile carrier. Ensure devices receive and install regular security updates, particularly baseband/LTE firmware updates.
- Consultation6.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 $5,568.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-9051 — 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-9051 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