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

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

In Android before 2018-04-05 or earlier security patch level on Qualcomm Snapdragon Automobile and Snapdragon Mobile SD 425, SD 430, SD 450, SD 625, SD 650/52, SD 820, and SD 820A, there is a TOCTOU vulnerability in the input validation for bulletin_board_read syscall. A pointer dereference is being validated without promising the pointer hasn't been changed by the HLOS program.

UnknownCVSS not scoredNot KEV-listedUpdatedSep 16, 2024, 23:46 UTC (UTC+00:00)

Security readout for executives and security teams

Older Android and automotive devices using specific Qualcomm Snapdragon chips may have a memory-checking flaw. The issue is tied to devices at Android security patch levels before 2018-04-05. Business urgency depends on whether legacy Qualcomm-based devices remain in use and cannot receive vendor firmware updates. Exposure is most likely in legacy Android, automotive, or embedded fleets using Qualcomm Snapdragon Automobile or Snapdragon Mobile SD 425, 430, 450, 625, 650/52, 820, or 820A with security patch levels before 2018-04-05. Medium operational priority for organizations with older Qualcomm-based Android or automotive assets. The vulnerability is old and not KEV-listed, but unsupported devices may remain permanently exposed if firmware updates are unavailable. Mitigation focus: Update affected devices to firmware with Android security patch level 2018-04-05 or later.; Check OEM, Android, and Qualcomm guidance for device-specific fix availability.; Remove or replace unsupported devices that cannot receive the relevant security patch..

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-10439 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 MobileSD 425, SD 430, SD 450, SD 625, SD 650/52, SD 820, SD 820AListed

Weakness

CWE details

No CWE listed

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