The getProcessRecordLocked method in services/core/java/com/android/server/am/ActivityManagerService.java in ActivityManager in Android bef…

published 2015-10-01 11y ago modified 2026-06-17 4mo ago also EUVD-2015-3880

cvss: 6.8; version 2.0, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 0.6%; EPSS 0.6% chance of exploitation in 30 days, percentile 46%
public exploits: 0; none known

The getProcessRecordLocked method in services/core/java/com/android/server/am/ActivityManagerService.java in ActivityManager in Android before 5.1.1 LMY48I allows attackers to trigger incorrect process loading via a crafted application, as demonstrated by interfering with use of the Settings application, aka internal bug 21669445.

Patch / fix

links 1

android.googlesource.com/platform/frameworks/base/+/e3cde784e3d99966f313fe00dcecf19… commit

Is CVE-2015-3844 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

0.55% chance of exploitation in the next 30 days, higher than 46% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
NVD	2.0	6.8	AV:N/AC:M/Au:N/C:P/I:P/A:P

Classification

Weakness

CWE-264 Permissions, Privileges, and Access Controls

References

android.googlesource.com /platform/frameworks/base/+/e3cde784e3d99966f313fe00dcecf191f6a44a31
vendor-advisory
groups.google.com /forum/message/raw?msg=android-security-updates/Ugvu3fi6RQM/yzJvoTVrIQAJ
mailing-list, vendor-advisory

Sources

CVE List CVE-2015-3844
NVD CVE-2015-3844

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.