CVE-2019-14041Public exploit

Kernel memory corruption via QSEECOM type race

Published Feb 7, 2020 · Updated Aug 5, 2024

A QSEECOM race condition in Qualcomm Snapdragon chipsets allows local users with device access to corrupt kernel memory. Concurrent QSEECOM ioctls can change the shared handle's type while __qseecom_update_cmd_buf processes it, mixing listener and client handling without consistent bounds assumptions. Exploitation requires access to /dev/qseecom; the demonstrated outcome is a kernel panic, while controlled memory corruption enables kernel privilege escalation.

CVSS severity7.8
High
EPSS probability0.43%
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

A QSEECOM race condition in Qualcomm Snapdragon chipsets allows local users with device access to corrupt kernel memory. Concurrent QSEECOM ioctls can change the shared handle's type while __qseecom_update_cmd_buf processes it, mixing listener and client handling without consistent bounds assumptions. Exploitation requires access to /dev/qseecom; the demonstrated outcome is a kernel panic, while controlled memory corruption enables kernel privilege escalation.

The record

CVE
CVE-2019-14041
Published
Feb 7, 2020
Updated
Aug 5, 2024
Vendor
Qualcomm
Product
Snapdragon
Classifications
CWE-120, T1068
Attack vector
local
Privileges
authenticated

Timeline

How it unfolded

  1. Feb 7, 2020CVE publishedPublication date reported by the CVE source.
  2. Aug 5, 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, MDM9206, MDM9207C, MDM9607, MDM9640, MDM9650, MSM8905, MSM8909W, MSM8917, MSM8953, MSM8996AU, Nicobar, QCM2150, QCS405, QCS605, QM215, Rennell, SA6155P, Saipan, SC8180X, SDA660, SDA845, SDM429, SDM429W, SDM439, SDM450, SDM632, 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, MDM9206, MDM9207C, MDM9607, MDM9640, MDM9650, MSM8905, MSM8909W, MSM8917, MSM8953, MSM8996AU, Nicobar, QCM2150, QCS405, QCS605, QM215, Rennell, SA6155P, Saipan, SC8180X, SDA660, SDA845, SDM429, SDM429W, SDM439, SDM450, SDM632, SDM670, SDM710, SDM845, SDX20, SDX24, SDX55, SM6150, SM7150, SM8150, SM8250, SXR1130, SXR2130

Published CVSS scores

7.8NVDCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
4.6NVDAV:L/AC:L/Au:N/C:P/I:P/A:P

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 exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-120Buffer Copy without Checking Size of Input ('Classic Buffer Overflow')
T1068Exploitation for Privilege Escalation

Public exploit references

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