In multiple locations, there is a possible way to corrupt memory due to a double free.

published 2023-12-04 2 y ago modified 2026-06-17 4 mo ago also EUVD-2023-44710

cvss: 7.8; version 3.1, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 0.2%; EPSS 0.2% chance of exploitation in 30 days, percentile 5%
public exploits: 0; none known

In multiple locations, there is a possible way to corrupt memory due to a double free. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

Patch / fix

links 4

CISA SSVC

Exploitation: none
Automatable: no
Technical impact: total
Assessed: 2 y ago (2024-08-28)

Exploit prediction

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

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

Affected products

Google Android

Classification

Weakness

CWE-415 Double Free

References

android.googlesource.com /platform/frameworks/base/+/e4a821b10a1b020f18fc6fc316b13b90fa450bae
mailing-list, patch
android.googlesource.com /platform/frameworks/base/+/58fa254a5d1aee2206de90d5396c01e177483e3a
mailing-list, patch
android.googlesource.com /platform/frameworks/base/+/c3bc12c484ef3bbca4cec19234437c45af5e584d
mailing-list, patch
source.android.com /security/bulletin/2023-12-01
patch, vendor-advisory

Sources

CVE List CVE-2023-40103
NVD CVE-2023-40103

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.

Summary