dbcve.org
Apq8098 FirmwareOperating system · Qualcomm

CVE-2020-11122

MEDIUM · 5.5 CVSS v3.1 Published 2020-09-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
58/100
Remediation priority · Elevated
No privileges

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
u'Null Pointer exception while playing crafted mkv file as data stream get deleted on secondary invalid configuration' in Snapdragon Auto, Snapdragon Consumer IOT, Snapdragon Mobile in APQ8098, Bitra, Kamorta, SA6155P, Saipan, SM6150, SM7150, SM8150, SM8250, SXR2130

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 · moderate confidence

A null pointer dereference vulnerability exists in Qualcomm Snapdragon chipsets when processing crafted MKV media files. The vulnerability is triggered when the data stream is deleted due to an invalid secondary configuration during MKV playback, causing a denial of service condition.

MitigationApply firmware updates from device/OEM vendors when available. Avoid processing untrusted or crafted MKV files from unknown sources as a temporary risk mitigation.

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
Apq8098 FirmwareOperating system
Affected:all versions
Bitra FirmwareOperating system
Affected:all versions
Kamorta FirmwareOperating system
Affected:all versions
Sa6155p FirmwareOperating system
Affected:all versions
Saipan FirmwareOperating system
Affected:all versions
Sm6150 FirmwareOperating system
Affected:all versions
Sm7150 FirmwareOperating system
Affected:all versions
Sm8150 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
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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 Qualcomm chipset model
    On Android devices, run 'getprop ro.board.platform' or 'getprop ro.hardware' in a shell. Alternatively, check /proc/cpuinfo for the processor identifier. On Linux systems, use 'lscpu' or check /sys/devices/system/cpu/ for chipset information.
    Affected if The chipset identifier matches one of the affected models: Apq8098, Bitra, Kamorta, Sa6155p, Saipan, Sm6150, Sm7150, or Sm8150.
  2. Confirm the firmware version is from the affected list
    Check the firmware or baseband version using 'getprop ro.build.id' or 'getprop ro.modem.version' on Android. Verify the specific firmware variant matches any of the affected products listed.
    Affected if The device firmware corresponds to any of the affected Qualcomm platforms listed in the CVE (all versions of Apq8098, Bitra, Kamorta, Sa6155p, Saipan, Sm6150, Sm7150, Sm8150).
  3. Check if MKV playback capability exists
    Query the media codec list on the device using 'adb shell dumpsys media.codec' on Android, or check /system/etc/media_codecs.xml for entries that include Matroska (MKV) support. Look for MKV-specific demuxer or decoder components.
    Affected if The device supports Matroska (MKV) container format decoding through its media framework.
  4. Verify media processing components are active
    Check if the mediaserver, media.codec, or Codec2 service is running using 'ps -A | grep -i media' or 'dumpsys media'. The vulnerability exists in the media stream processing pipeline.
    Affected if The media server or codec services are actively running and capable of processing incoming media streams.

A device is affected if it uses any of the listed Qualcomm chipsets (Apq8098, Bitra, Kamorta, Sa6155p, Saipan, Sm6150, Sm7150, Sm8150) with all firmware versions and has MKV media playback capability enabled in the media framework.

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 firmware updates from device/OEM vendors when available. Avoid processing untrusted or crafted MKV files from unknown sources as a temporary risk mitigation.

Fix this in Apq8098 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,460
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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