LiveActive security incident?Get immediate response
CVE Record

CVE-2018-13925: Error in parsing PMT table frees the memory allocated for the map section but does not reset the context ma...

Error in parsing PMT table frees the memory allocated for the map section but does not reset the context map section reference causing heap use after free issue in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon IoT, Snapdragon Mobile, Snapdragon Wearables in MDM9206, MDM9607, MDM9650, MSM8909W, MSM8996AU, QCS605, Qualcomm 215, SD 210/SD 212/SD 205, SD 425, SD 427, SD 430, SD 435, SD 439 / SD 429, SD 450, SD 600, SD 615/16/SD 415, SD 625, SD 632, SD 636, SD 650/52, SD 712 / SD 710 / SD 670, SD 820, SD 820A, SD 835, SD 845 / SD 850, SD 855, SDA660, SDM439, SDM630, SDM660, SDX20, 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-13925 is a Qualcomm Snapdragon memory-safety flaw. During PMT table parsing, memory can be freed while an internal reference is left pointing to it. That creates a heap use-after-free condition in affected Snapdragon platforms used across mobile, auto, IoT, wearable, compute, and connectivity devices.

Executive priority

Prioritize as an asset and firmware governance issue, not as confirmed emergency exploitation. The affected hardware range is broad, but public details are limited. Focus on identifying dependent devices, checking OEM patch availability, and reducing exposure from unsupported embedded devices.

Technical view

The published description identifies an error in PMT table parsing: the map-section allocation is freed, but the context map-section reference is not reset. Subsequent use of that stale reference can cause heap use after free. The source bundle does not provide CVSS, attack vector, privileges, or impact details.

Likely exposure

Exposure is most likely in products containing the listed Qualcomm chipsets or Snapdragon platform families, including embedded IoT, mobile, wearable, auto, connectivity, and compute devices. Actual exposure depends on the OEM firmware version, whether the vulnerable component is present, and vendor remediation status.

Exploitation context

The source bundle does not cite active exploitation, public exploit code, or CISA KEV listing. Treat exploitation status as unconfirmed. Research should focus on whether deployed devices include affected Qualcomm components and whether their OEM firmware has incorporated Qualcomm security bulletin guidance.

Researcher notes

Evidence is limited to the CVE description and Qualcomm bulletin reference. No CVSS, CWE, patch text, or exploitability metrics are included in the source bundle. Avoid assuming reachable attack surface. Validate whether PMT parsing exists in the target firmware and whether OEM updates include Qualcomm remediation.

Mitigation direction

  • Check Qualcomm's product security bulletin for vendor guidance on CVE-2018-13925.
  • Obtain firmware or security updates from the device OEM or carrier.
  • Inventory devices using the listed Snapdragon platforms and chipsets.
  • Prioritize unmanaged IoT, auto, mobile, and connectivity devices for vendor review.
  • Retire or isolate devices that cannot receive OEM-supported firmware updates.

Validation and detection

  • Map asset hardware to the affected Qualcomm chipset list.
  • Record OEM model, firmware build, carrier build, and patch level for each device.
  • Compare firmware status against Qualcomm and OEM security advisories.
  • Confirm updates were installed through OEM management or device telemetry.
  • Document unsupported devices requiring isolation, replacement, or risk acceptance.
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-13925 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 IOT, Snapdragon Industrial IOT, Snapdragon IoT, Snapdragon Mobile, Snapdragon WearablesMDM9206, MDM9607, MDM9650, MSM8909W, MSM8996AU, QCS605, Qualcomm 215, SD 210/SD 212/SD 205, SD 425, SD 427, SD 430, SD 435, SD 439 / SD 429, SD 450, SD 600, SD 615/16/SD 415, SD 625, SD 632, SD 636, SD 650/52, SD 712 / SD 710 / SD 670, SD 820, SD 820A, SD 835, SD 845 / SD 850, SD 855, SDA660, SDM439, SDM630, SDM660, SDX20, 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.