LiveActive security incident?Get immediate response
CVE Record

CVE-2018-11968: Improper check before assigning value can lead to integer overflow in Snapdragon Auto, Snapdragon Compute,...

Improper check before assigning value can lead to integer overflow in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon IoT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wired Infrastructure and Networking in IPQ4019, IPQ8064, IPQ8074, MDM9206, MDM9607, MDM9640, MDM9650, MSM8996AU, QCA4020, QCA6174A, QCA6564, QCA6574, QCA6574AU, QCA6584, QCA6584AU, QCA8081, QCA9377, QCA9379, QCA9531, QCA9558, QCA9563, QCA9880, QCA9886, QCA9980, QCN5502, QCS605, SD 210/SD 212/SD 205, SD 425, SD 427, SD 430, SD 435, SD 450, SD 600, SD 625, SD 636, SD 675, SD 712 / SD 710 / SD 670, SD 820, SD 820A, SD 835, SD 845 / SD 850, SD 855, SD 8CX, SDA660, SDM630, SDM660, SDX20, SDX24, SM7150, Snapdragon_High_Med_2016, SXR1130

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2018-11968 is a Qualcomm Snapdragon vulnerability where an improper value check can cause integer overflow. The source bundle lists many Snapdragon chipsets across mobile, IoT, automotive, networking, and compute products. Business urgency depends on whether your deployed devices use affected Qualcomm components and whether OEM firmware guidance applies.

Executive priority

Prioritize discovery first. The affected component list is broad, but the supplied sources lack severity and exploitability detail. Leadership should require asset mapping, vendor guidance checks, and firmware update status before assigning emergency remediation resources.

Technical view

The issue is described as an improper check before assigning a value, leading to integer overflow in numerous Qualcomm Snapdragon product families and chipsets. The supplied data does not include CVSS, CWE, attack vector, impact type, prerequisites, or fixed firmware versions, so technical severity cannot be reliably scored from these sources alone.

Likely exposure

Exposure is most likely in devices or embedded products using the listed Qualcomm chipsets, including Snapdragon mobile, IoT, automotive, networking, connectivity, and compute platforms. CPEs are not provided, so exposure must be mapped through hardware BOMs, device models, firmware inventories, and OEM advisories.

Exploitation context

The source bundle does not identify active exploitation, and this CVE is not marked as CISA KEV. No cited source in the bundle provides exploit availability, attack path, required privileges, or network reachability. Treat exploitation status as unconfirmed, not absent.

Researcher notes

Key gaps are CVSS, CWE, attack vector, impact, affected firmware branches, and fixed versions. The Qualcomm reference is the primary remediation source, but the bundle only cites the bulletin anchor. Avoid assuming exploitability until vendor or independent evidence confirms conditions.

Mitigation direction

  • Check Qualcomm and OEM security bulletins for device-specific guidance.
  • Apply vendor-provided firmware or driver updates where available.
  • Prioritize internet-facing, managed, or safety-relevant devices using listed chipsets.
  • Track unsupported devices for replacement or compensating controls.
  • Document affected asset decisions and residual risk.

Validation and detection

  • Inventory devices for the listed Qualcomm chipsets and product families.
  • Map device models to OEM firmware and security bulletin status.
  • Confirm current firmware versions against vendor remediation guidance.
  • Review asset exposure, management interfaces, and business criticality.
  • Record systems where vendor fix information is unavailable.
Prepared
Confidence
medium
Sources
3

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-2018-11968 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.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Qualcomm, Inc.Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon IoT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wired Infrastructure and NetworkingIPQ4019, IPQ8064, IPQ8074, MDM9206, MDM9607, MDM9640, MDM9650, MSM8996AU, QCA4020, QCA6174A, QCA6564, QCA6574, QCA6574AU, QCA6584, QCA6584AU, QCA8081, QCA9377, QCA9379, QCA9531, QCA9558, QCA9563, QCA9880, QCA9886, QCA9980, QCN5502, QCS605, SD 210/SD 212/SD 205, SD 425, SD 427, SD 430, SD 435, SD 450, SD 600, SD 625, SD 636, SD 675, SD 712 / SD 710 / SD 670, SD 820, SD 820A, SD 835, SD 845 / SD 850, SD 855, SD 8CX, SDA660, SDM630, SDM660, SDX20, SDX24, SM7150, Snapdragon_High_Med_2016, SXR1130Listed
Weakness

CWE details

No CWE listed

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