CVE-2020-11152
CVE-2020-11152 is a medium-severity vulnerability in Qualcomm Apq8009w with a CVSS 3.x base score of 6.4. 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: Medium (CVSS 3.x base score 6.4)
- CVSS v2: 6.9
- EPSS exploit prediction: 0% (3rd percentile)
- Actively exploited: Not listed in CISA KEV
- Weakness: CWE-362
- Affected product: Qualcomm Apq8009w
- Published:
- Last modified:
Description
Race condition in HAL layer while processing callback objects received from HIDL due to lack of synchronization between accessing objects in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables
Frequently asked questions
- What is CVE-2020-11152?
- Race condition in HAL layer while processing callback objects received from HIDL due to lack of synchronization between accessing objects in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables
- How severe is CVE-2020-11152?
- CVE-2020-11152 has a CVSS 3.x base score of 6.4, rated medium severity. It is exploitable over local access with high attack complexity, requires high privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
- Is CVE-2020-11152 being actively exploited?
- It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (3rd percentile), an estimate of the probability of exploitation in the next 30 days.
- What products are affected by CVE-2020-11152?
- CVE-2020-11152 primarily affects Qualcomm Apq8009w. In total, 160 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
- How do I fix CVE-2020-11152?
- Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
- When was CVE-2020-11152 published?
- CVE-2020-11152 was published on 2021-01-21 and last updated on 2026-06-17.
References
- https://www.qualcomm.com/company/product-security/bulletins/december-2020-bulletin
- https://www.qualcomm.com/company/product-security/bulletins/december-2020-security-bulletin
Affected products (160)
- cpe:2.3:h:qualcomm:apq8009w:-:*:*:*:*:*:*:*
- cpe:2.3:h:qualcomm:apq8017:-:*:*:*:*:*:*:*
- cpe:2.3:h:qualcomm:apq8037:-:*:*:*:*:*:*:*
- cpe:2.3:h:qualcomm:apq8052:-:*:*:*:*:*:*:*
- cpe:2.3:h:qualcomm:apq8053:-:*:*:*:*:*:*:*
- cpe:2.3:h:qualcomm:apq8056:-:*:*:*:*:*:*:*
- cpe:2.3:h:qualcomm:apq8076:-:*:*:*:*:*:*:*
- cpe:2.3:h:qualcomm:apq8096au:-:*:*:*:*:*:*:*
- cpe:2.3:h:qualcomm:aqt1000:-:*:*:*:*:*:*:*
- cpe:2.3:h:qualcomm:ar8031:-:*:*:*:*:*:*:*
- cpe:2.3:h:qualcomm:csra6620:-:*:*:*:*:*:*:*
- cpe:2.3:h:qualcomm:csra6640:-:*:*:*:*:*:*:*
- cpe:2.3:h:qualcomm:msm8909w:-:*:*:*:*:*:*:*
- cpe:2.3:h:qualcomm:msm8916:-:*:*:*:*:*:*:*
- cpe:2.3:h:qualcomm:msm8917:-:*:*:*:*:*:*:*
- cpe:2.3:h:qualcomm:msm8920:-:*:*:*:*:*:*:*
- cpe:2.3:h:qualcomm:msm8937:-:*:*:*:*:*:*:*
- cpe:2.3:h:qualcomm:msm8940:-:*:*:*:*:*:*:*
- cpe:2.3:h:qualcomm:msm8952:-:*:*:*:*:*:*:*
- cpe:2.3:h:qualcomm:msm8953:-:*:*:*:*:*:*:*
- cpe:2.3:h:qualcomm:msm8956:-:*:*:*:*:*:*:*
- cpe:2.3:h:qualcomm:msm8976:-:*:*:*:*:*:*:*
- cpe:2.3:h:qualcomm:msm8976sg:-:*:*:*:*:*:*:*
- cpe:2.3:h:qualcomm:msm8996au:-:*:*:*:*:*:*:*
- cpe:2.3:h:qualcomm:pm439:-:*:*:*:*:*:*:*
- cpe:2.3:h:qualcomm:pm660:-:*:*:*:*:*:*:*
- cpe:2.3:h:qualcomm:pm660a:-:*:*:*:*:*:*:*
- cpe:2.3:h:qualcomm:pm660l:-:*:*:*:*:*:*:*
- cpe:2.3:h:qualcomm:pm670:-:*:*:*:*:*:*:*
- cpe:2.3:h:qualcomm:pm670a:-:*:*:*:*:*:*:*
- cpe:2.3:h:qualcomm:pm670l:-:*:*:*:*:*:*:*
- cpe:2.3:h:qualcomm:pm8004:-:*:*:*:*:*:*:*
- cpe:2.3:h:qualcomm:pm8005:-:*:*:*:*:*:*:*
- cpe:2.3:h:qualcomm:pm855:-:*:*:*:*:*:*:*
- cpe:2.3:h:qualcomm:pm855a:-:*:*:*:*:*:*:*
- cpe:2.3:h:qualcomm:pm855b:-:*:*:*:*:*:*:*
- cpe:2.3:h:qualcomm:pm855l:-:*:*:*:*:*:*:*
- cpe:2.3:h:qualcomm:pm855p:-:*:*:*:*:*:*:*
- cpe:2.3:h:qualcomm:pm8916:-:*:*:*:*:*:*:*
- cpe:2.3:h:qualcomm:pm8937:-:*:*:*:*:*:*:*
More vulnerabilities in Qualcomm Apq8009w
- CVE-2020-11283 — Critical (CVSS 9.8): A buffer overflow can occur when playing an MKV clip due to lack of input validation in Snapdragon Auto, Snapdragon…
- CVE-2020-3691 — Critical (CVSS 9.8): Possible out of bound memory access in audio due to integer underflow while processing modified contents in Snapdragon…
- CVE-2020-3686 — Critical (CVSS 9.8): Possible memory out of bound issue during music playback when an incorrect bit stream content is copied into array…
- CVE-2020-11216 — Critical (CVSS 9.8): Buffer over read can happen in video driver when playing clip with atomsize having value UINT32_MAX in Snapdragon Auto,…
- CVE-2020-11213 — Critical (CVSS 9.8): Out of bound reads might occur in while processing Service descriptor due to improper validation of length of fields in…
- CVE-2020-11197 — Critical (CVSS 9.8): Possible integer overflow can occur when stream info update is called when total number of streams detected are zero…
All CVEs affecting Qualcomm Apq8009w →
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…