LiveActive security incident?Get immediate response
CVE Record

CVE-2013-6123: Multiple array index errors in drivers/media/video/msm/server/msm_cam_server.c in the MSM camera driver for...

Multiple array index errors in drivers/media/video/msm/server/msm_cam_server.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, allow attackers to gain privileges by leveraging camera device-node access, related to the (1) msm_ctrl_cmd_done, (2) msm_ioctl_server, and (3) msm_server_send_ctrl functions.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This is an old Android/Qualcomm MSM camera-driver flaw that could let someone with access to the camera device node gain higher privileges on the device. It is not described as a remote network issue. The provided sources do not identify active exploitation or a complete affected-product list.

Executive priority

Prioritize if the organization still operates legacy Qualcomm MSM Android devices, especially shared, kiosk, field, or unmanaged devices. For modern supported fleets, urgency depends on whether any deployed kernel lineage includes this driver and lacks the vendor fixes.

Technical view

CVE-2013-6123 covers multiple array index errors in drivers/media/video/msm/server/msm_cam_server.c in Linux kernel 3.x MSM camera driver code, including msm_ctrl_cmd_done, msm_ioctl_server, and msm_server_send_ctrl. The stated impact is privilege escalation through camera device-node access.

Likely exposure

Likely exposure is legacy Android/MSM devices using Qualcomm Innovation Center MSM camera-driver contributions in Linux kernel 3.x. The bundle does not name specific OEM devices, firmware versions, or CPEs, so exposure must be confirmed from device kernels and vendor advisories.

Exploitation context

The sources describe privilege gain requiring camera device-node access. KEV is false, and the provided bundle does not cite active exploitation. Treat this as a local or app-context privilege-escalation risk on vulnerable devices, not as proven internet-exploited activity.

Researcher notes

Evidence is limited to CVE metadata, CodeAurora advisory and commits, and IBM X-Force indexing. The bundle lacks CVSS, CWE mapping, precise version ranges, affected OEM device names, exploit details, and confirmation of real-world exploitation.

Mitigation direction

  • Review the CodeAurora advisory and linked commits for vendor patch context.
  • Update affected device firmware or kernel to a vendor-patched build.
  • Restrict camera device-node access according to vendor guidance where updates are unavailable.
  • Retire unsupported legacy MSM Android devices that cannot receive kernel fixes.

Validation and detection

  • Inventory Android devices using Qualcomm MSM kernels or QuIC MSM camera-driver code.
  • Check kernel source or build provenance for msm_cam_server.c exposure.
  • Confirm whether linked CodeAurora fixes are present in the deployed kernel.
  • Review device-node permissions for camera access on managed devices.
  • Check OEM security bulletins for device-specific remediation status.
Prepared
Confidence
medium
Sources
6

Public sources used

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-6123 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
5Source links

CVSS and timeline data

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

Source materials

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.