How severe is CVE-2019-2260?

CVE-2019-2260 has a CVSS 3.x base score of 7.0, rated high severity. It is exploitable over local access with high attack complexity, requires low privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.

Is CVE-2019-2260 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (4th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2019-2260?

CVE-2019-2260 primarily affects Qualcomm Mdm9150 Firmware. In total, 39 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.

How do I fix CVE-2019-2260?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

When was CVE-2019-2260 published?

CVE-2019-2260 was published on 2019-07-22 and last updated on 2026-06-17.

CVE-2019-2260

CVE-2019-2260 is a high-severity vulnerability in Qualcomm Mdm9150 Firmware with a CVSS 3.x base score of 7.0. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-362.

Key facts

Severity: High (CVSS 3.x base score 7.0)
CVSS v2: 6.9
EPSS exploit prediction: 0% (4th percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-362
Affected product: Qualcomm Mdm9150 Firmware
Published: 2019-07-22
Last modified: 2026-06-17

Description

A race condition occurs while processing perf-event which can lead to a use after free condition in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables in MDM9150, MDM9206, MDM9607, MDM9640, MDM9650, MSM8909W, QCS405, 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 632, SD 636, SD 665, SD 712 / SD 710 / SD 670, SD 730, SD 820A, SD 835, SD 845 / SD 850, SD 855, SDM439, SDM630, SDM660, SDX20, SDX24, Snapdragon_High_Med_2016, SXR1130

Frequently asked questions

What is CVE-2019-2260?: A race condition occurs while processing perf-event which can lead to a use after free condition in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables in MDM9150, MDM9206, MDM9607, MDM9640, MDM9650, MSM8909W, QCS405, 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 632, SD 636, SD 665, SD 712 / SD 710 / SD 670, SD 730, SD 820A, SD 835, SD 845 / SD 850, SD 855, SDM439, SDM630, SDM660, SDX20, SDX24, Snapdragon_High_Med_2016, SXR1130
How severe is CVE-2019-2260?: CVE-2019-2260 has a CVSS 3.x base score of 7.0, rated high severity. It is exploitable over local access with high attack complexity, requires low privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2019-2260 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (4th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2019-2260?: CVE-2019-2260 primarily affects Qualcomm Mdm9150 Firmware. In total, 39 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2019-2260?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2019-2260 published?: CVE-2019-2260 was published on 2019-07-22 and last updated on 2026-06-17.

References

https://www.codeaurora.org/security-bulletin/2019/06/03/june-2019-code-aurora-security-bulletin

Affected products (39)

cpe:2.3:o:qualcomm:mdm9150_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:qualcomm:mdm9206_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:qualcomm:mdm9607_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:qualcomm:mdm9640_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:qualcomm:mdm9650_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:qualcomm:msm8909w_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:qualcomm:qcs405_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:qualcomm:qcs605_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:qualcomm:qualcomm_215_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:qualcomm:sd_210_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:qualcomm:sd_212_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:qualcomm:sd_205_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:qualcomm:sd_425_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:qualcomm:sd_427_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:qualcomm:sd_430_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:qualcomm:sd_435_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:qualcomm:sd_439_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:qualcomm:sd_429_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:qualcomm:sd_450_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:qualcomm:sd_625_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:qualcomm:sd_632_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:qualcomm:sd_636_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:qualcomm:sd_665_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:qualcomm:sd_712_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:qualcomm:sd_710_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:qualcomm:sd_670_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:qualcomm:sd_730_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:qualcomm:sd_820a_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:qualcomm:sd_835_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:qualcomm:sd_845_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:qualcomm:sd_850_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:qualcomm:sd_855_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:qualcomm:sdm439_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:qualcomm:sdm630_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:qualcomm:sdm660_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:qualcomm:sdx20_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:qualcomm:sdx24_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:qualcomm:snapdragon_high_med_2016_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:qualcomm:sxr1130_firmware:-:*:*:*:*:*:*:*

More vulnerabilities in Qualcomm Mdm9150 Firmware

CVE-2022-40510 — Critical (CVSS 9.8): Memory corruption due to buffer copy without checking size of input in Audio while voice call with EVS vocoder.
CVE-2022-25720 — Critical (CVSS 9.8): Memory corruption in WLAN due to out of bound array access during connect/roaming in Snapdragon Auto, Snapdragon…
CVE-2022-25651 — Critical (CVSS 9.8): Memory corruption in bluetooth host due to integer overflow while processing BT HFP-UNIT profile in Snapdragon Auto,…
CVE-2021-35104 — Critical (CVSS 9.8): Possible buffer overflow due to improper parsing of headers while playing the FLAC audio clip in Snapdragon Auto,…
CVE-2021-30351 — Critical (CVSS 9.8): An out of bound memory access can occur due to improper validation of number of frames being passed during music…
CVE-2021-1975 — Critical (CVSS 9.8): Possible heap overflow due to improper length check of domain while parsing the DNS response in Snapdragon Auto,…

All CVEs affecting Qualcomm Mdm9150 Firmware →

Other CWE-362 (Race Condition) vulnerabilities

CVE-2022-27626 — Critical (CVSS 10.0): A vulnerability regarding concurrent execution using shared resource with improper synchronization ('Race Condition')…
CVE-2015-8556 — Critical (CVSS 10.0): Local privilege escalation vulnerability in the Gentoo QEMU package before 2.5.0-r1.
CVE-2014-0703 — Critical (CVSS 10.0): Cisco Wireless LAN Controller (WLC) devices 7.4 before 7.4.110.0 distribute Aironet IOS software with a race condition…
CVE-2010-1228 — Critical (CVSS 10.0): Multiple race conditions in the sandbox infrastructure in Google Chrome before 4.1.249.1036 have unspecified impact and…
CVE-2008-6598 — Critical (CVSS 10.0): Multiple race conditions in WANPIPE before 3.3.6 have unknown impact and attack vectors related to "bri restart logic."
CVE-2026-46137 — Critical (CVSS 9.8): In the Linux kernel, the following vulnerability has been resolved: mptcp: pm: ADD_ADDR rtx: fix potential…

Browse all CWE-362 (Race Condition) vulnerabilities →