CVE-2021-39793: Google Pixel Out-of-Bounds Write
Google Pixel · listed in the CISA catalog of actively exploited vulnerabilities since 2022-04-11.
- CVSS v3.1 (CISA ADP)
- 7.8
- high
- EPSS (exploit probability, 30 days)
- 0.7%
- higher than 53.5% of all CVEs
- Added to CISA KEV
- 2022-04-11
- US federal due date 2022-05-02
- Automatable (CISA SSVC)
- no
- technical impact: total
CVE-2021-39793 explained
CVE-2021-39793 is an out-of-bounds write in the kbase_jd_user_buf_pin_pages function of mali_kbase_mem.c in the Android kernel used on Google Pixel devices. A logic error lets a local attacker escalate privileges without user interaction. CISA lists it as known to be exploited, so patching affected devices is a priority.
Impact
An attacker who can already run code with low privileges on the device can escalate privileges locally. No additional execution privileges and no user interaction are needed. Confidentiality, integrity and availability impacts are all high. CISA rates the technical impact as total, meaning full control of the affected component. Exploitation is not automatable, but attackers are known to use this vulnerability.
Who is affected
The CVE record lists Android, with the affected version given in free text as Android kernel. The issue concerns Google Pixel devices. The CVE record names no fixed version. Check the vendor advisory for the security update that contains the fix.
Written with AI from the data on this page and checked against it automatically.
Official 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
CISA required action: Apply updates per vendor instructions.
CISA notes
Affected and fixed versions
From the CVE record published by the vendor or CVE numbering authority.
- AndroidAffectedFixed in
- Android kernel
not statedVersion statement as published by the CNA (free text).
| Product | Affected | Fixed in |
|---|---|---|
| AndroidVersion statement as published by the CNA (free text). |
| not stated |
How to fix it
- The CVE record names no fixed version – check the vendor advisory and CISA's required action for updates and mitigations.
- Vendor advisory: source.android.com/security/bulletin/pixel/2022-03-01
- CISA's deadline for US federal agencies: 2022-05-02 (passed) – a useful benchmark for everyone else, too.
What to do
- Install the latest Android security update for Pixel devices as described in the vendor advisory.
- Follow CISA's required action: apply updates per vendor instructions.
- Use device management to verify that all Pixel devices have the update installed.
- Limit installation of untrusted apps, since exploitation requires local code execution.
- Review devices that stayed unpatched for signs of compromise.
The CVE record names no fixed version. Follow the vendor advisory to identify and install the Android security update that addresses this issue, as CISA requires: apply updates per vendor instructions. Until devices are updated, restrict installation of untrusted apps and prioritize updating exposed or high-value devices.
Written with AI from the data on this page and checked against it automatically.
CISA's assessment (SSVC)
- Exploitation
- Exploited in the wild
- Automatable
- No – each attack needs manual steps
- Technical impact
- Total – full control of the component or total information disclosure
Weakness: CWE-787 Out-of-bounds Write
Questions about CVE-2021-39793
- Is CVE-2021-39793 being exploited?
- Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2022-04-11, with a US federal due date of 2022-05-02. Whether it has been used in ransomware is unknown.
- Can it be exploited remotely?
- No. The attack vector is local and requires low privileges, such as code running on the device. No user interaction is needed, and CISA rates it as not automatable.
- What should we do about it?
- Apply the Android security update for Pixel devices per the vendor's instructions, as CISA requires, and confirm that all managed devices are patched.
Written with AI from the data on this page and checked against it automatically.
References
Trackers and catalogs
Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-22. Always confirm with the vendor's or distribution's advisory before patching.