CVE-2016-10424: Qualcomm, Inc. Snapdragon Automobile, Snapdragon…

CVE-2016-10424: In Android before 2018-04-05 or earlier security patch level on Qualcomm Snapdragon Automobile, Snapdragon...

In Android before 2018-04-05 or earlier security patch level on Qualcomm Snapdragon Automobile, Snapdragon Mobile, and Snapdragon Wear MDM9206, MDM9650, SD 210/SD 212/SD 205, SD 410/12, SD 425, SD 430, SD 450, SD 615/16/SD 415, SD 617, SD 625, SD 650/52, SD 800, SD 808, SD 820, SD 820A, SD 835, SD 845, and SD 850, upgrading LibPNG from 1.6.12 to 1.6.21 fixes multiple issues with different CWEs.

UnknownCVSS not scoredNot KEV-listedUpdatedSep 17, 2024, 01:25 UTC (UTC+00:00)

Security readout for executives and security teams

This CVE concerns Android devices using listed Qualcomm Snapdragon platforms where an older LibPNG version had multiple unresolved issues. The source bundle names the affected chipsets and says the issue is fixed by moving LibPNG from 1.6.12 to 1.6.21 in Android patch levels after April 5, 2018. Exposure is most likely in older Android, automotive, mobile, or wearable devices using the listed Snapdragon platforms and missing the April 5, 2018 Android security patch level or equivalent OEM firmware update. Treat this as a legacy-device patch governance issue. The business risk depends on whether affected Qualcomm-based devices remain in service without the April 2018 Android security patch or equivalent OEM firmware. Mitigation focus: Update affected Android devices to the 2018-04-05 security patch level or later.; Use OEM firmware containing the Qualcomm/Android LibPNG 1.6.21 fix.; Check Qualcomm and device-vendor guidance for model-specific update availability..

Prepared: Jun 7, 2026, 13:40 UTC (UTC+00:00)

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-2016-10424 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: Apr 18, 2018, 14:00 UTC (UTC+00:00)

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

CVE List V5 sourceCVE List V5
https://source.android.com/security/bulletin/2018-04-01CVE reference · x_refsource_CONFIRM

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus

Qualcomm, Inc.Snapdragon Automobile, Snapdragon Mobile, Snapdragon WearMDM9206, MDM9650, SD 210/SD 212/SD 205, SD 410/12, SD 425, SD 430, SD 450, SD 615/16/SD 415, SD 617, SD 625, SD 650/52, SD 800, SD 808, SD 820, SD 820A, SD 835, SD 845, SD 850Listed

Weakness

CWE details

No CWE listed

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