Linux KernelOperating system · Linux
CVE-2015-0568
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 · uneditedUse-after-free vulnerability in the msm_set_crop function in drivers/media/video/msm/msm_camera.c in the MSM-Camera driver for the Linux kernel 3.x, as used in Qualcomm Innovation Center (QuIC) Android contributions for MSM devices and other products, allows attackers to gain privileges or cause a denial of service (memory corruption) via an application that makes a crafted ioctl call.
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 confidenceUse-after-free vulnerability in the msm_set_crop function in the MSM-Camera driver (drivers/media/video/msm/msm_camera.c) for Linux kernel 3.x. The flaw is triggered via a crafted ioctl call, allowing an attacker to reference freed memory, potentially leading to privilege escalation or memory corruption and denial of service.
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
>= 3.0, <= 3.19.8CVSS 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
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/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 kernel versionRun 'uname -r' or 'cat /proc/version' to obtain the running kernel versionAffected if Kernel version is 3.0.x through 3.19.8 inclusive (e.g., 3.4.0, 3.10.23, 3.18.5)
-
Verify MSM-Camera driver configurationCheck if CONFIG_MSM_CAMERA is enabled in kernel config: 'grep CONFIG_MSM_CAMERA /boot/config-$(uname -r)' or look in /proc/config.gz'Affected if The MSM_CAMERA config option is set to 'y' (built-in) or 'm' (module)
-
Locate the vulnerable driver sourceCheck if the driver file exists in the kernel source tree: 'ls -la /lib/modules/$(uname -r)/build/drivers/media/video/msm/msm_camera.c' or search the kernel headersAffected if The file drivers/media/video/msm/msm_camera.c exists in the installed kernel or headers
-
Check for driver module presenceRun 'lsmod | grep msm_camera' or check /sys/module/ for msm_camera entries on devices with MSM camera hardwareAffected if The msm_camera module is loaded or built into the kernel on MSM-based devices (common in Android phones/tablets using Qualcomm Snapdragon processors)
A system is affected if it runs a Linux kernel between 3.0 and 3.19.8 with the MSM-Camera driver compiled in or loaded on Qualcomm MSM hardware.
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 kernel/driver patches; update to a patched Linux kernel version (3.x) and device-specific camera driver firmware. For embedded/Android devices, obtain OTA updates from the device manufacturer that include the patched MSM-Camera driver.
Fix this in Linux Kernel
Scoped from the published advisory
- 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-0568 — 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-0568 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