CVE-2021-39793
CVE-2021-39793 is a high-severity vulnerability (CVSS 3.1 base score 7.8). Google Pixel contains a possible out-of-bounds write due to a logic error in the code that could lead to local escalation of privilege. CISA added it to the Known Exploited Vulnerabilities catalog on 2022-04-11, with a remediation due date of 2022-05-02 for US federal civilian agencies. As of 2026-11-22, EPSS estimates a 0.7% probability of exploitation in the next 30 days, in the 53rd percentile of scored CVEs.
Updated
- CVSS 3.1
- 7.8 HIGH
- EPSS
- 0.7% (53rd pct)
- CISA KEV
- Exploited
- Published
- 2022-03-16
- Weakness
- CWE-787
Google Pixel Out-of-Bounds Write Vulnerability is confirmed as actively exploited and is listed in the CISA KEV catalog.
Required action
Apply updates per vendor instructions.
CISA notes
https://nvd.nist.gov/vuln/detail/CVE-2021-39793
Description
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
Key Findings
as of 2026-11-22- CISA added CVE-2021-39793 to the KEV catalog 26 days after its CVE record was published.
- It is one of 77 Google entries in the CISA KEV catalog, and one of 21 added in 2022.
- Its current EPSS score (0.7%) is higher than that of 1% of CISA KEV entries.
Severity
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HOpen in CVSS calculator Remediation Timeline
BOD 26-04, US federal agenciesDeadlines for US federal civilian agencies under Table 1 of CISA BOD 26-04, from the CVE's KEV status (listed) and CISA's SSVC values (automatable no, technical impact total, 2025-01-29).
How the timeline is set
Table 1 of CISA's Binding Operational Directive 26-04 sets the time US federal civilian agencies have to remediate a vulnerability. It depends on four inputs: whether the asset is publicly exposed, whether the CVE is in the KEV catalog, whether an adversary can automate its exploitation, and whether exploitation gives partial or total control of the asset, which SSVC calls technical impact. CISA publishes the last three for every CVE through services such as its Vulnrichment program.
Days are calendar days. The clock starts at whichever comes first: CISA adds the CVE to the KEV catalog, or the agency identifies the vulnerability on an asset and reports it to its Continuous Diagnostics and Mitigation (CDM) dashboard. A publicly exposed asset is accessible to unauthenticated or untrusted entities via public networks, such as the internet. Forensic triage means assessing the asset to determine whether it has been compromised.
CISA calculates the KEV due date with the same table, using its own evidence on whether the vulnerability is present in a publicly exposed asset. Each agency makes the final exposure decision for each of its assets.
Affected Products
| Vendor | Product | Affected versions |
|---|---|---|
| - | Android | Android kernel |
References
1 linksOther references
Record Details
- Published
- 2022-03-16
- Last updated
- 2025-10-21
- Assigner (CNA)
- google_android
- Credited to
- -
More from Google
Google Pixel Improper Authorization Vulnerability
Google Chromium WebP Heap-Based Buffer Overflow Vulnerability
Out-of-Bounds Write in Google Brotli Decoder
Google Chromium V8 Remote Code Execution Vulnerability
CVE record data © The MITRE Corporation, used under the CVE Terms of Use. Exploited-in-the-wild data from the CISA Known Exploited Vulnerabilities catalog (CC0). Exploit prediction scores by FIRST EPSS (first.org/epss). Alert titles and links from CISA cybersecurity alerts. This site is not affiliated with or endorsed by MITRE, NVD, CISA, or FIRST.