CVE-2022-22071
Qualcomm Multiple Chipsets Use-After-Free Vulnerability
Qualcomm Multiple Chipsets
Possible use after free when process shell memory is freed using IOCTL munmap call and process initialization is in progress in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music
Exploitation status
CISA Known Exploited Vulnerabilities
Listed by CISA on 5 December 2023. US federal agencies were required to remediate it by 26 December 2023.
EPSS — exploitation probability
FIRST puts the probability of exploitation activity in the next 30 days at 0.4%, which is higher than 33.8% of all scored vulnerabilities. EPSS is a forecast of activity, not a measure of severity, and it is rescored daily.
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Frequently asked questions
Is CVE-2022-22071 being exploited by ransomware groups?
No ransomware group in this database is currently recorded as exploiting CVE-2022-22071.
What does CVE-2022-22071 affect?
CVE-2022-22071 affects Qualcomm Multiple Chipsets. Possible use after free when process shell memory is freed using IOCTL munmap call and process initialization is in progress in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music
How severe is CVE-2022-22071?
CVE-2022-22071 is rated HIGH with a CVSS base score of 8.4. EPSS puts the probability of exploitation in the next 30 days at 0.4%, higher than 33.8% of all scored vulnerabilities. It is listed in the CISA Known Exploited Vulnerabilities catalog, with a federal remediation deadline of 26 December 2023.
How should organisations respond to CVE-2022-22071?
Apply the vendor patch for Qualcomm Multiple Chipsets as the first priority, and treat any internet-facing instance as the most urgent. Because this vulnerability is associated with ransomware activity, also review whether the affected systems were reachable before patching, rather than assuming that patching alone closes the incident.