LiveActive security incident?Get immediate response
CVE Record

CVE-2014-7252: Multiple unspecified vulnerabilities in the Syslink driver for Texas Instruments OMAP mobile processor, as...

Multiple unspecified vulnerabilities in the Syslink driver for Texas Instruments OMAP mobile processor, as used on NTT DOCOMO ARROWS Tab LTE F-01D, ARROWS X LTE F-05D, Disney Mobile on docomo F-08D, REGZA Phone T-01D, and PRADA phone by LG L-02D; and SoftBank SHARP handsets 102SH allow local users to execute arbitrary code or read kernel memory via unknown vectors related to userland data and "improper data validation."

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

CVE-2014-7252 affects a Syslink driver used with Texas Instruments OMAP mobile processors in several older Japanese carrier Android devices. A local user could run arbitrary code or read kernel memory. Business urgency is mainly for organizations still owning, managing, or accepting these legacy devices. Exposure appears limited to listed legacy mobile devices: NTT DOCOMO ARROWS, Disney Mobile, REGZA, PRADA phone models, and SoftBank SHARP 102SH. Standard servers, desktops, and unrelated Android devices are not identified as affected in the supplied sources. Treat this as a legacy mobile asset exposure issue, not a broad enterprise emergency. Priority should be higher if affected devices can access corporate mail, VPN, privileged apps, or regulated data. Mitigation focus: Identify whether any listed legacy devices remain in inventory or BYOD access paths.; Check JVN, device vendor, and carrier guidance for model-specific updates or retirement advice.; Remove affected devices from sensitive networks if updates cannot be verified..

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-2014-7252 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
1Source 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.