LiveActive security incident?Get immediate response
CVE Record

CVE-2015-0568: Use-after-free vulnerability in the msm_set_crop function in drivers/media/video/msm/msm_camera.c in the MS...

Use-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.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

This is a Linux kernel camera-driver memory bug affecting Qualcomm MSM Android-related camera code. A malicious local application could trigger memory corruption through a crafted ioctl call, potentially gaining higher privileges or crashing the device. The provided sources do not identify specific OEM device models, patch levels, or confirmed exploitation. Exposure is most likely on older Android devices or vendor kernels using Qualcomm MSM camera driver code derived from the affected Linux 3.x QuIC contributions. The provided source bundle lists affected vendor and product as n/a, so exact device scope must be confirmed through OEM or kernel build evidence. Prioritize this for legacy mobile or embedded fleets using Qualcomm MSM Android kernels. Business urgency is high where devices handle sensitive data and cannot be patched, but lower for environments without affected devices. No active exploitation is evidenced in the provided sources. Mitigation focus: Check Qualcomm, CodeAurora, Android, and OEM guidance for CVE-2015-0568 fixes.; Update affected Android firmware or vendor kernel when a trusted vendor fix exists.; Prioritize retirement or isolation of unsupported MSM Android devices..

Prepared

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2015-0568 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.