CVE-2018-11816

MediaServer heap use-after-free via crafted Binder request

Published Nov 26, 2024 · Updated Nov 26, 2024

Use-after-free in Qualcomm Snapdragon MediaServer allows local users with low privileges to corrupt heap memory via a crafted Binder request. Qualcomm identifies MediaServer's Binder request handling as the locus but has not published the faulty lifetime-management operation. Reachability requires a locally running low-privilege process, and public material does not distinguish a MediaServer crash from code execution.

CVSS severity7.8
High
EPSS probability0.11%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Use-after-free in Qualcomm Snapdragon MediaServer allows local users with low privileges to corrupt heap memory via a crafted Binder request. Qualcomm identifies MediaServer's Binder request handling as the locus but has not published the faulty lifetime-management operation. Reachability requires a locally running low-privilege process, and public material does not distinguish a MediaServer crash from code execution.

The record

CVE
CVE-2018-11816
Published
Nov 26, 2024
Updated
Nov 26, 2024
Vendor
Qualcomm
Product
Snapdragon 820 Firmware
Classifications
CWE-416, T1068
Attack vector
local
Privileges
authenticated

Timeline

How it unfolded

  1. Nov 26, 2024CVE publishedPublication date reported by the CVE source.
  2. Nov 26, 2024Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=0 <=*

What conditions does exploitation require?

Attack vectorlocal
Required privilegesauthenticated

What is affected?

Qualcomm · Snapdragon 820 Firmwareversion=0 <=*
Qualcomm · APQ8016 Firmwareversion=0 <=*
Qualcomm · Snapdragon 670 Firmwareversion=0 <=*
Qualcomm · Snapdragonversion=9206 LTE Modem; version=APQ8016; version=APQ8017; version=APQ8039; version=APQ8052; version=APQ8056; version=APQ8076; version=AQT1000; version=AR6003; version=SD660; version=SD670; version=SD820; version=SD821; version=SD835
Qualcomm · MDM9206 LTE Modem Firmwareversion=0 <=*
Qualcomm · Snapdragon 660 Firmwareversion=0 <=*
Qualcomm · Snapdragon 821 Firmwareversion=0 <=*
Qualcomm · APQ8052 Firmwareversion=0 <=*
Qualcomm · APQ8039 Firmwareversion=0 <=*
Qualcomm · APQ8076 Firmwareversion=0 <=*
Qualcomm · APQ8017 Firmwareversion=0 <=*
Qualcomm · Snapdragon 835 Firmwareversion=0 <=*
Qualcomm · APQ8056 Firmwareversion=0 <=*
Qualcomm · AQT1000 Firmwareversion=0 <=*
Qualcomm · AR6003 Firmwareversion=0 <=*

Published CVSS scores

7.8Qualcomm, Inc.CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorlocal
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-416Use After Free
T1068Exploitation for Privilege Escalation

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo