dbcve.org
Linux KernelOperating system · Linux

CVE-2017-0583

HIGH · 7.0 CVSS v3.0 Published 2017-04-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
73/100
Remediation priority · Elevated
No privileges

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 · unedited
An elevation of privilege vulnerability in the Qualcomm CP access driver could enable a local malicious application to execute arbitrary code within the context of the kernel. This issue is rated as Moderate because it first requires compromising a privileged process and because of vulnerability specific details which limit the impact of the issue. Product: Android. Versions: Kernel-3.10, Kernel-3.18. Android ID: A-32068683. References: QC-CR#1103788.

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 confidence

Elevation of privilege vulnerability in the Qualcomm CP (Communication Processor) access driver allows a local malicious application to execute arbitrary code within the kernel context. The flaw exists in kernel-3.10 and kernel-3.18 versions on Android devices with affected Qualcomm processors. Exploitation requires first compromising a privileged process, which somewhat limits the overall impact despite the kernel-level code execution capability.

MitigationApply the January 2017 Android Security Bulletin patch or later security updates that address this vulnerability in the Qualcomm CP access driver. Devices running affected kernel versions should be updated to patched firmware.

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
Linux KernelOperating system
Affected:= 3.10= 3.18

CVSS 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
High
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:L/AC:H/PR:N/UI:R/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the kernel version
    Run 'uname -r' or check /proc/version to see the running kernel version
    Affected if The kernel version is exactly 3.10 or 3.18 (these are the only affected versions listed)
  2. Confirm Android OS
    Check if the system is Android by looking for /system/build.prop or running 'getprop ro.build.version.release'
    Affected if The device runs Android and has an affected kernel version
  3. Verify Qualcomm processor
    Check /proc/cpuinfo for Qualcomm Snapdragon chipset or run 'getprop ro.hardware' to identify the device hardware
    Affected if The device uses a Qualcomm processor and has an affected kernel version
  4. Check for the CP access driver
    Look for the Qualcomm CP access driver module in /sys/module/ or check kernel config for CONFIG_QCOM_CP access driver support
    Affected if The Qualcomm CP access driver is loaded or compiled into the kernel on an affected version
  5. Verify patch status
    Check the Android security patch level via 'getprop ro.build.version.security_patch' or check the firmware build date
    Affected if The security patch level is earlier than January 2017 or the device has not received the January 2017 Android Security Bulletin patch

A device is affected if it is an Android device with a Qualcomm processor running an unmodified kernel version 3.10 or 3.18 that has not received the January 2017 security patch.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the January 2017 Android Security Bulletin patch or later security updates that address this vulnerability in the Qualcomm CP access driver. Devices running affected kernel versions should be updated to patched firmware.

Fix this in Linux Kernel Scoped from the published advisory
  • Consultation8.0 h
  • Implementation40.0 h
  • Testing24.0 h
  • Review / QA16.0 h
88.0 hours of engineering $15,280
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $24,448.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-0583 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2017-0583 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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