Description
In binder_thread_read 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-116855682References: Upstream kernel
Published: 2019-06-19
Score: 7.8 High
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

No analysis available yet.

Remediation

No remediation available yet.

Tracking

Sign in to view the affected projects.

Advisories
Source ID Title
EUVD EUVD EUVD-2019-11667 In binder_thread_read 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-116855682References: Upstream kernel
History

No history.

cve-icon MITRE

Status: PUBLISHED

Assigner: google_android

Published:

Updated: 2024-08-04T18:35:52.397Z

Reserved: 2018-12-10T00:00:00.000Z

Link: CVE-2019-2025

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Modified

Published: 2019-06-19T21:15:10.760

Modified: 2026-06-17T02:33:07.757

Link: CVE-2019-2025

cve-icon Redhat

Severity : Low

Publid Date: 2019-03-04T00:00:00Z

Links: CVE-2019-2025 - Bugzilla

cve-icon OpenCVE Enrichment

No data.

Weaknesses
  • CWE-119

    Improper Restriction of Operations within the Bounds of a Memory Buffer

  • CWE-362

    Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')

  • CWE-416

    Use After Free

  • CWE-667

    Improper Locking