LiveActive security incident?Get immediate response
CVE Record

CVE-2012-4220: diagchar_core.c in the Qualcomm Innovation Center (QuIC) Diagnostics (aka DIAG) kernel-mode driver for Andr...

diagchar_core.c in the Qualcomm Innovation Center (QuIC) Diagnostics (aka DIAG) kernel-mode driver for Android 2.3 through 4.2 allows attackers to execute arbitrary code or cause a denial of service (incorrect pointer dereference) via an application that uses crafted arguments in a local diagchar_ioctl call.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

This is an old Android kernel driver flaw in Qualcomm/QuIC Diagnostics. A local app could crash the device or potentially run code with high privileges by passing crafted arguments to the driver. The sources identify Android 2.3 through 4.2, so exposure is mainly legacy Android estates, embedded devices, and unsupported phones or tablets. Likely limited to legacy Android 2.3 through 4.2 devices using the Qualcomm/QuIC DIAG kernel driver. Modern managed Android fleets are less likely exposed, but old embedded Android devices, lab hardware, or unsupported mobile endpoints may remain at risk. Prioritize this where legacy Android devices still support business operations. The issue is old and local, but kernel-level arbitrary code execution or device denial of service can be material on unmanaged, embedded, or unsupported Android assets. Mitigation focus: Check Qualcomm, CodeAurora, and device OEM guidance for patched firmware.; Retire or replace Android 2.3 through 4.2 devices where feasible.; Restrict installation of untrusted local applications on potentially affected 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.

description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2012-4220 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.