CVE-2015-6640

The prctl_set_vma_anon_name function in kernel/sys.c in Android before 5.1.1 LMY49F and 6.0 before 2016-01-01 does not ensure that only one vma is accessed in a certain update action, which allows attackers to gain privileges or cause a denial of service (vma list corruption) via a crafted application, aka internal bug 20017123.

Published: 2016-01-06 Last update: 2026-06-16 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2015-6640 is rated Moderate Risk (49.1/100): CVSS High severity, with low exploitation likelihood (EPSS 0.73%). Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2015-6640

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.10% 0.73% +0.62%
2 2025-07-03 0.20% 0.10% -0.10%
3 2025-03-30 — 0.20% —

Full EPSS history (11 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2015-6640

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.8 3.0 HIGH
CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 1.8 5.9 [email protected]
9.3 2.0 HIGH
AV:N/AC:M/Au:N/C:C/I:C/A:C Click to expand
Access vector (AV:N)
Can be exploited remotely over network reachability.
Access complexity (AC:M)
Exploitation needs some favorable conditions, but not exceptional ones.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:C)
Complete confidentiality impact.
Integrity impact (I:C)
Complete integrity impact.
Availability impact (A:C)
Complete availability impact.
 8.6 10.0 [email protected]

Weakness enumeration for CVE-2015-6640

OS Trackers for CVE-2015-6640

vendor priority summary link
ubuntu medium CVE-2015-6640 medium priority: Ubuntu including 34 source packages (android, linux, …), 313 status rows across 10 suites (artful, bionic, precise, trusty, upstream, vivid, wily, xenial, yakkety, zesty): DNE 214, not-affected 71, ignored 17, needs-triage 11. https://ubuntu.com/security/CVE-2015-6640

Affected software / configurations for CVE-2015-6640

Vendor Product Version Raw CPE
google android 4.4.4 cpe:2.3:o:google:android:4.4.4:*:*:*:*:*:*:*
google android 5.0 cpe:2.3:o:google:android:5.0:*:*:*:*:*:*:*
google android 5.1.1 cpe:2.3:o:google:android:5.1.1:*:*:*:*:*:*:*
google android 6.0 cpe:2.3:o:google:android:6.0:*:*:*:*:*:*:*

References for CVE-2015-6640

cvelogic Threat Intelligence