dbcve.org
Msm8909w FirmwareOperating system · Qualcomm

CVE-2019-2273

HIGH · 7.5 CVSS v3.0 Published 2019-07-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
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
IOMMU page fault while playing h265 video file leads to denial of service issue in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables in MSM8909W, QCS605, Qualcomm 215, SD 210/SD 212/SD 205, SD 425, SD 427, SD 430, SD 435, SD 439 / SD 429, SD 450, SD 625, SD 650/52, SD 665, SD 675, SD 712 / SD 710 / SD 670, SD 730, SD 820, SD 845 / SD 850, SD 855, SD 8CX, SDM439, Snapdragon_High_Med_2016, SXR1130

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

A vulnerability in the IOMMU (Input-Output Memory Management Unit) implementation in Qualcomm Snapdragon chipsets allows a specially crafted H265 video file to trigger a page fault during video playback, causing a denial of service (device crash or freeze). The issue stems from improper memory handling in the video playback path.

MitigationApply vendor-provided firmware/patch updates from Qualcomm and downstream device OEMs. Users should avoid playing untrusted H265 video files until the device firmware is updated.

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
Msm8909w FirmwareOperating system
Affected:all versions
Qcs605 FirmwareOperating system
Affected:all versions
Qualcomm 215 FirmwareOperating system
Affected:all versions
Sd 210 FirmwareOperating system
Affected:all versions
Sd 212 FirmwareOperating system
Affected:all versions
Sd 205 FirmwareOperating system
Affected:all versions
Sd 425 FirmwareOperating system
Affected:all versions
Sd 427 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
None
Integrity
None
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 device chipset model
    Check the device or system information to determine the Qualcomm Snapdragon chipset variant (e.g., Msm8909w, Qcs605, Qualcomm 215, Sd 210, Sd 212, Sd 205, Sd 425, or Sd 427)
    Affected if The chipset matches any of the affected models: Msm8909w, Qcs605, Qualcomm 215, Sd 210, Sd 212, Sd 205, Sd 425, or Sd 427
  2. Check firmware version
    Retrieve the firmware version from the device system settings, bootloader, or via AT command (for mobile devices) or appropriate firmware query method for the specific hardware
    Affected if Firmware is present on any of the affected chipset models (all firmware versions of these chipsets are affected)
  3. Verify H265 video decoding capability
    Check if the device or software supports H265 (HEVC) video decoding - look for H265/HEVC decoder libraries, video player capabilities, or codec support in the system
    Affected if H265 video playback capability is present and enabled on the device
  4. Confirm IOMMU is active in video playback path
    Verify that IOMMU is enabled in the kernel boot parameters or device configuration, and that video playback utilizes IOMMU-protected memory regions
    Affected if IOMMU is enabled and the video subsystem uses IOMMU-protected memory buffers for H265 playback

The environment is affected if the device uses any of the listed Qualcomm Snapdragon chipset models (Msm8909w, Qcs605, Qualcomm 215, Sd 210, Sd 212, Sd 205, Sd 425, or Sd 427) with firmware that supports H265 video playback and has IOMMU enabled for the video subsystem.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor-provided firmware/patch updates from Qualcomm and downstream device OEMs. Users should avoid playing untrusted H265 video files until the device firmware is updated.

Fix this in Msm8909w Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Testing8.0 h
  • Review / QA4.0 h
16.0 hours of engineering $2,720
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-2273 — 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-2019-2273 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