Skip to content
Fencer Vulns
high 7.4

CVE-2019-2213 json

In binder_free_transaction of binder.c, there is a possible use-after-free due to a race condition.

published 2019-11-13 6 y ago modified 2026-06-17 4 mo ago also EUVD-2019-11855

cvss
7.4
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.1%
EPSS 0.1% chance of exploitation in 30 days, percentile 3%
public exploits
0
none known

Summary

In binder_free_transaction of binder.c, there is a possible use-after-free due to a race condition. 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-133758011References: Upstream kernel

Patch / fix

  • linux Debian 14, Debian 13, Debian 12 5.2.6-1

debian advisories DEBIAN-CVE-2019-2213

  • linux Ubuntu 18.04 LTS 4.15.0-60.67
  • linux-aws Ubuntu 18.04 LTS 4.15.0-1047.49
  • linux-gcp Ubuntu 16.04 LTS 4.15.0-1041.43
  • linux-gcp Ubuntu 18.04 LTS 4.15.0-1042.45
  • linux-hwe Ubuntu 16.04 LTS 4.15.0-60.67~16.04.1
  • linux-hwe Ubuntu 18.04 LTS 5.0.0-31.33~18.04.1
  • linux-kvm Ubuntu 18.04 LTS 4.15.0-1043.43
  • linux-oem Ubuntu 18.04 LTS 4.15.0-1056.65

ubuntu advisories UBUNTU-CVE-2019-2213

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

Exploit prediction

0.15% chance of exploitation in the next 30 days, higher than 3% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
NVD 3.1 7.4 CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 6.9 AV:L/AC:M/Au:N/C:C/I:C/A:C

Affected products

  • n/a Android

Classification

Weakness
  • CWE-362 Concurrent Execution using Shared Resource with Improper Synchronization
  • CWE-416 Use After Free

References

Sources

Fencer Vulns 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.