CVE-2019-10567Known exploitationPublic exploit

Kernel code execution via GPU ringbuffer corruption

Published Feb 7, 2020 · Updated Aug 4, 2024

Privilege escalation in Qualcomm Snapdragon GPU drivers on listed chipsets allows local users to execute code in the kernel. A writable shared scratch buffer lets user-supplied GPU commands corrupt the ringbuffer read pointer, overwrite queued commands, disable protected mode, and replace TTBR0 for arbitrary physical-memory access. Access from an Android application sandbox is sufficient, and successful exploitation grants kernel-level code execution.

CVSS severity7.8
High
EPSS probability0.25%
Next 30 days · Sep 16, 2026
Known exploitationReported
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

Privilege escalation in Qualcomm Snapdragon GPU drivers on listed chipsets allows local users to execute code in the kernel. A writable shared scratch buffer lets user-supplied GPU commands corrupt the ringbuffer read pointer, overwrite queued commands, disable protected mode, and replace TTBR0 for arbitrary physical-memory access. Access from an Android application sandbox is sufficient, and successful exploitation grants kernel-level code execution.

The record

CVE
CVE-2019-10567
Published
Feb 7, 2020
Updated
Aug 4, 2024
Vendor
Qualcomm
Product
Snapdragon
Classifications
T1404
Attack vector
local
Privileges
authenticated

Timeline

How it unfolded

  1. Feb 7, 2020CVE publishedPublication date reported by the CVE source.
  2. Aug 4, 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=APQ8009, APQ8017, APQ8053, APQ8096AU, APQ8098, MDM9150, MDM9206, MDM9207C, MDM9607, MDM9650, MSM8909W, MSM8917, MSM8920, MSM8937, MSM8940, MSM8953, MSM8996AU, MSM8998, Nicobar, QCS405, QCS605, QM215, Rennell, SA6155P, Saipan, SC8180X, SDA660, SDA845, SDM429, SDM429W, SDM439, SDM450, SDM630, SDM632, SDM636, SDM660, SDM670, SDM710, SDM845, SDX20, SDX24, SDX55, SM6150, SM7150, SM8150, SM8250, SXR1130, SXR2130

What conditions does exploitation require?

Attack vectorlocal
Required privilegesauthenticated

What is affected?

Qualcomm · Snapdragonversion=APQ8009, APQ8017, APQ8053, APQ8096AU, APQ8098, MDM9150, MDM9206, MDM9207C, MDM9607, MDM9650, MSM8909W, MSM8917, MSM8920, MSM8937, MSM8940, MSM8953, MSM8996AU, MSM8998, Nicobar, QCS405, QCS605, QM215, Rennell, SA6155P, Saipan, SC8180X, SDA660, SDA845, SDM429, SDM429W, SDM439, SDM450, SDM630, SDM632, SDM636, SDM660, SDM670, SDM710, SDM845, SDX20, SDX24, SDX55, SM6150, SM7150, SM8150, SM8250, SXR1130, SXR2130

Published CVSS scores

7.2NIST NVDAV:L/AC:L/Au:N/C:C/I:C/A:C
7.8NIST NVDCVSS: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 9, 2026Sep 15, 2026
Latest reporting daySep 15, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorlocal
Privilegesauthenticated
Known exploitationReported
Public exploitPublished

Weakness, pattern, technique

T1404Exploitation for Privilege Escalation

Public exploit references

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

Reported exploitation

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