dbcve.org
Sd 210 FirmwareOperating system · Qualcomm

CVE-2016-10458

CRITICAL · 9.8 CVSS v3.0 Published 2018-04-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
In Android before 2018-04-05 or earlier security patch level on Qualcomm Snapdragon Mobile SD 210/SD 212/SD 205, SD 410/12, SD 425, SD 427, SD 430, SD 435, SD 450, SD 615/16/SD 415, SD 617, SD 625, SD 650/52, SD 808, SD 810, SD 820, SD 835, SD 845, SDM630, SDM636, SDM660, SDX20, and Snapdragon_High_Med_2016, the 'proper' solution for this will be to ensure that any users of qsee_log in the bootchain (before Linux boots) unallocate their buffers and clear the qsee_log pointer. Until support for that is implemented in TZ and the bootloader, enable tz_log to avoid potential scribbling. This solution will prevent the linux kernel memory corruption.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Memory corruption vulnerability in the qsee_log component of Trusted Execution Environment (TZ) on multiple Qualcomm Snapdragon chipsets. During the boot chain (before Linux loads), qsee_log buffers are not properly deallocated, causing them to be overwritten and leading to Linux kernel memory corruption.

MitigationEnable tz_log instead of qsee_log in the Trusted Execution Environment (TZ) and bootloader to prevent buffer overflow and memory corruption in the Linux kernel.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Sd 210 FirmwareOperating system
Affected:all versions
Sd 212 FirmwareOperating system
Affected:all versions
Sd 205 FirmwareOperating system
Affected:all versions
Sd 410 FirmwareOperating system
Affected:all versions
Sd 412 FirmwareOperating system
Affected:all versions
Sd 425 FirmwareOperating system
Affected:all versions
Sd 430 FirmwareOperating system
Affected:all versions
Sd 450 FirmwareOperating system
Affected:all versions

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the Qualcomm Snapdragon chipset model
    Check /proc/cpuinfo or boot logs for the chipset identifier (e.g., SD210, SD212, SD205, SD410, SD412, SD425, SD430, SD450)
    Affected if The device uses any of the listed affected Snapdragon variants (Sd 210, 212, 205, 410, 412, 425, 430, 450)
  2. Determine the firmware version
    Check the baseband/firmware version via AT commands, boot logs, or /proc/version. For Android devices, check Settings > About Phone > Build Number or use 'getprop' commands
    Affected if All firmware versions for the affected chipsets are vulnerable (no version is patched)
  3. Inspect the TEE configuration for qsee_log usage
    Examine boot logs (dmesg, /proc/bootlog, or early boot serial console output) for references to 'qsee_log' or 'tz_log' configuration in the Trusted Execution Environment
    Affected if qsee_log is enabled or referenced in the TZ configuration (vulnerable state)
  4. Review kernel memory corruption indicators
    Check kernel logs (dmesg, /var/log/kern.log) for messages related to TZ/qsee memory corruption, unexpected kernel panics, or memory overwrite errors occurring early in boot
    Affected if Memory corruption errors related to qsee_log or TZ buffer overflows appear in kernel logs

A user is affected if their device uses a Qualcomm Snapdragon Sd 210/212/205/410/412/425/430/450 chipset with qsee_log enabled in the Trusted Execution Environment, as all firmware versions for these chipsets contain the vulnerability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Enable tz_log instead of qsee_log in the Trusted Execution Environment (TZ) and bootloader to prevent buffer overflow and memory corruption in the Linux kernel.

Recommended fix Moderate confidence

Android security patch level 2018-04-05 or later from OEM (exact version varies by device manufacturer)

  1. 1. Verify the current Android security patch level on the affected device (Settings > About Phone > Security patch level)
  2. 2. If the security patch level is earlier than 2018-04-05, update the device to the latest Android security update available from the device OEM
  3. 3. As a configuration workaround mentioned in the advisory: ensure tz_log is enabled in the boot configuration to prevent qsee_log buffer scribbling that leads to kernel memory corruption
  4. 4. Contact the device OEM to confirm they have incorporated the Qualcomm fix addressing the qsee_log buffer handling in TrustZone (TZ) and bootloader components
Caveat OEM-specific updates may have additional changes; verify with device vendor before applying

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Sd 210 Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation24.0 h
  • Testing16.0 h
  • Review / QA8.0 h
56.0 hours of engineering $9,760
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $15,616.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2016-10458 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2016-10458 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data