ZeroDay Findings
Sign inSign up

Findings

CVE-2022-20421

In binder_inc_ref_for_node of binder.c, there is a possible way to corrupt memory due to a use after free.

Published Oct 11, 2022 · updated Oct 14, 2026 · google android

In binder_inc_ref_for_node of binder.c, there is a possible way to corrupt memory due to a use after free. 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-239630375References: Upstream kernel

Timeline

Detection, updates, and resolution for this record.

  1. Oct 11, 2022 · NIST NVD

    Detected

    In binder_inc_ref_for_node of binder.c, there is a possible way to corrupt memory due to a use after free. 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-239630375References: Upstream kernel

  2. Oct 14, 2026 · NIST NVD

    Updated

    In binder_inc_ref_for_node of binder.c, there is a possible way to corrupt memory due to a use after free. 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-239630375References: Upstream kernel

Affected

  • cpe debian/debian linux10.0
  • cpe debian/debian linux11.0
  • cpe google/androidversion unspecified

Sources

  • CVE.orgCVE-2022-20421

    Official CVE identifier

    cve.org
  • NIST NVDCVE-2022-20421

    In binder_inc_ref_for_node of binder.c, there is a possible way to corrupt memory due to a use after free. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: An

    nvd.nist.gov

References

CVE-2022-20421 · ZeroDay Findings