In unix_scm_to_skb of af_unix.c, there is a possible use after free bug due to a race condition.
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Listed in CISA KEV
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Actively exploited
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
The Android kernel's Unix domain socket code (af_unix.c) is affected by a use-after-free flaw caused by a race condition. A local attacker with system-level privileges could exploit it to escalate their privileges, and no user interaction is required.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
In unix_scm_to_skb of af_unix.c, there is a possible use after free bug due to a race condition. This could lead to local escalation of privilege with System execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android kernelAndroid ID: A-196926917References: Upstream kernel
Timeline
- CVE published
- Added to CISA KEV
CISA has evidence of exploitation in the wild
- CISA remediation deadline
Due date for US federal agencies to patch
- Record last updated
Affected versions
- n/a Android
Android kernel
References 2
source.android.com
lists.debian.org
Questions about CVE-2021-0920
What does this mean?
A race condition in the Linux kernel's AF_UNIX local socket code can cause memory to be used after it has been freed. The advisory says a local user could cause memory corruption or a crash (denial of service), and possibly gain elevated privileges.Source: lists.debian.org
Am I affected, and how do I check?
The product is listed as Android, but the facts give no affected version ranges. To check a device, look at its security patch level under Settings > About phone and compare it with the vendor's bulletin for this CVE.Source: lists.debian.org
What should I do about it?
No fix is listed in the facts provided. Check the vendor's advisory for a patched build and install it once your device offers it.Source: lists.debian.org
Is it being exploited?
Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2022-05-23, which means it has evidence of attacks. No public exploit code is tracked.Source: cisa.gov, cve.now feed data
What if there's no patch?
The facts provided do not list a workaround. Until a fix is confirmed, follow the vendor's advisory for any mitigation it publishes.Source: lists.debian.org