CVE-2021-39793
Google Pixel Out-of-Bounds Write Vulnerability
Google Pixel
In kbase_jd_user_buf_pin_pages of mali_kbase_mem.c, there is a possible out of bounds write due to a logic error in the code. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android kernelAndroid ID: A-210470189References: N/A
Exploitation status
CISA Known Exploited Vulnerabilities
Listed by CISA on 11 April 2022. US federal agencies were required to remediate it by 2 May 2022.
EPSS — exploitation probability
FIRST puts the probability of exploitation activity in the next 30 days at 0.7%, which is higher than 52.1% 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:L/UI:N/S:U/C:H/I:H/A:H
Frequently asked questions
Is CVE-2021-39793 being exploited by ransomware groups?
No ransomware group in this database is currently recorded as exploiting CVE-2021-39793.
What does CVE-2021-39793 affect?
CVE-2021-39793 affects Google Pixel. In kbase_jd_user_buf_pin_pages of mali_kbase_mem.c, there is a possible out of bounds write due to a logic error in the code. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android kernelAndroid ID: A-210470189References: N/A
How severe is CVE-2021-39793?
CVE-2021-39793 is rated HIGH with a CVSS base score of 7.8. EPSS puts the probability of exploitation in the next 30 days at 0.7%, higher than 52.1% of all scored vulnerabilities. It is listed in the CISA Known Exploited Vulnerabilities catalog, with a federal remediation deadline of 2 May 2022.
How should organisations respond to CVE-2021-39793?
Apply the vendor patch for Google Pixel 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.