LiveActive security incident?Get immediate response
CVE Record

CVE-2013-4738: Multiple stack-based buffer overflows in the MSM camera driver for the Linux kernel 3.x, as used in Qualcom...

Multiple stack-based buffer overflows 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, allow attackers to gain privileges via (1) a crafted VIDIOC_MSM_VPE_DEQUEUE_STREAM_BUFF_INFO ioctl call, related to drivers/media/platform/msm/camera_v2/pproc/vpe/msm_vpe.c, or (2) a crafted VIDIOC_MSM_CPP_DEQUEUE_STREAM_BUFF_INFO ioctl call, related to drivers/media/platform/msm/camera_v2/pproc/cpp/msm_cpp.c.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

CVE-2013-4738 describes stack buffer overflows in a Qualcomm MSM Android camera driver. A local attacker could potentially gain higher privileges on affected MSM devices. The public bundle gives no CVSS score, no KEV listing, and unclear product/version boundaries, so exposure must be verified against device kernel sources and OEM support information. Most relevant exposure is legacy Android or embedded products using Qualcomm MSM kernels that include the vulnerable camera_v2 pproc VPE/CPP driver code. The bundle does not identify exact device models, Android builds, or fixed versions. Prioritize if the organization still operates legacy Qualcomm MSM Android or embedded devices. For supported, current devices, urgency depends on vendor confirmation. The main business risk is local compromise becoming deeper device control. Mitigation focus: Check OEM, Qualcomm, or CodeAurora guidance for affected kernels and fixed builds.; Update affected Android or embedded device firmware when a supported fix exists.; Retire or isolate unsupported legacy MSM devices if no vendor update is available..

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-2013-4738 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.