CVE-2020-11231

CVE-2020-11231 is a medium-severity vulnerability in Qualcomm Apq8017 Firmware with a CVSS 3.x base score of 6.7. 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-415.

Key facts

Description

Two threads call one or both functions concurrently leading to corruption of pointers and reference counters which in turn can lead to heap corruption in Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile

Frequently asked questions

What is CVE-2020-11231?
Two threads call one or both functions concurrently leading to corruption of pointers and reference counters which in turn can lead to heap corruption in Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile
How severe is CVE-2020-11231?
CVE-2020-11231 has a CVSS 3.x base score of 6.7, rated medium severity. It is exploitable over local access with low attack complexity, requires high privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2020-11231 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (5th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2020-11231?
CVE-2020-11231 primarily affects Qualcomm Apq8017 Firmware. In total, 215 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2020-11231?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
When was CVE-2020-11231 published?
CVE-2020-11231 was published on 2021-04-07 and last updated on 2026-06-17.

References

Affected products (215)

More vulnerabilities in Qualcomm Apq8017 Firmware

All CVEs affecting Qualcomm Apq8017 Firmware →

Other CWE-415 (Double Free) vulnerabilities

Browse all CWE-415 (Double Free) vulnerabilities →