CVE-2019-2025
In binder_thread_read of binder.c, there is a possible use-after-free due to improper locking.
Does this matter?
A public exploit is published in Exploit-DB (verified) and the impact is high, while EPSS rates exploitation at 0.5%. Anyone can run this; patch or mitigate before the next change window and check exposed instances for signs of use.
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
- CVSS 3.0
- 7.8 HIGHCVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- EPSS
- 0.52% probability · 44th percentile
- Public exploits
- 1 in Exploit-DB · verified · first 6 March 2019
- CISA KEV
- Not listed
- Weakness
- CWE-416, CWE-667
- Affected
- google/android
- Source
- security@android.com
EPSS 0.5% since 26 October 2026; no change recorded yet. Points are recorded when the score first appears and whenever it moves by a percentage point or more.
Public exploits (1)
Entries in Exploit-DB that cite this CVE. Links go to the Exploit-DB page and to the file in the public repository; nothing is hosted here. A verified tick means the Exploit-DB team confirmed the exploit works against the stated version.
References
- https://source.android.com/security/bulletin/2019-03-01Vendor Advisory
- https://source.android.com/security/bulletin/2019-03-01Vendor Advisory
Source: NVD record, EPSS from FIRST.org, KEV from CISA, exploits from Exploit-DB. Refreshed daily. Download this record as JSON.