CVE-2019-1999 json
In binder_alloc_free_page of binder_alloc.c, there is a possible double free due to improper locking.
published 2019-02-28 7 y ago modified 2026-06-17 4 mo ago also EUVD-2019-10556
- cvss
- 7.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.8%
- EPSS 0.8% chance of exploitation in 30 days, percentile 57%
- public exploits
- 1
- Exploit-DB
Summary
In binder_alloc_free_page of binder_alloc.c, there is a possible double 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: Android. Versions: Android kernel. Android ID: A-120025196.
Patch / fix
- linux Debian 14, Debian 13, Debian 12 5.2.6-1
debian advisories DEBIAN-CVE-2019-1999
- linux-aws-fips Ubuntu Pro FIPS-updates 18.04 LTS 4.15.0-2018.18
- linux-azure-fips Ubuntu Pro FIPS-updates 18.04 LTS 4.15.0-2006.7
ubuntu advisories UBUNTU-CVE-2019-1999
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
Timeline
- First public exploit (EDB-46357)
- Published
Exploit prediction
0.81% chance of exploitation in the next 30 days, higher than 57% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-46357 Android - binder Use-After-Free of VMA via race Between reclaim and munmap dos, 2019-02-12
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 7.2 | AV:L/AC:L/Au:N/C:C/I:C/A:C |
Affected products
- Android Android
Classification
- Weakness
-
- CWE-415 Double Free
References
-
exploit-db.com
/exploits/46357/
exploit, third-party-advisory, vdb-entry
-
usn.ubuntu.com
/3979-1/
vendor-advisory, third-party-advisory
-
debian.org
/security/2019/dsa-4495
vendor-advisory, third-party-advisory
-
source.android.com
/security/bulletin/2019-02-01
vendor-advisory
-
securityfocus.com
/bid/106851
vdb-entry, broken-link
-
seclists.org
/bugtraq/2019/Aug/13
mailing-list, third-party-advisory
Sources
- CVE List CVE-2019-1999
- NVD CVE-2019-1999
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.