What is the severity of CVE-2015-6640?

CVE-2015-6640 has a high severity rating due to its potential to allow privilege escalation and denial of service.

How do I fix CVE-2015-6640?

To resolve CVE-2015-6640, you should update your Android device to version 6.0 or later.

What versions of Android are affected by CVE-2015-6640?

CVE-2015-6640 affects Android versions 4.4.4, 5.0, 5.1.1, and all versions before 6.0.

Can CVE-2015-6640 lead to data loss?

Yes, CVE-2015-6640 can potentially lead to data loss due to vma list corruption.

Who is impacted by CVE-2015-6640?

Users of older Android versions prior to 6.0 are at risk of being impacted by CVE-2015-6640.

Vulnerability/
CVE-2015-6640

critical

9.3

CWE

264

4/1/2016

6/1/2016

26/8/2024

CVE-2015-6640

First published: Mon Jan 04 2016(Updated: )

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.

Credit: security@android.com

Affected Software	Affected Version	How to fix
Google Android
Google Android	=4.4.4
Google Android	=5.0
Google Android	=5.1.1
Google Android	=6.0

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2015-6640?
CVE-2015-6640 has a high severity rating due to its potential to allow privilege escalation and denial of service.
How do I fix CVE-2015-6640?
To resolve CVE-2015-6640, you should update your Android device to version 6.0 or later.
What versions of Android are affected by CVE-2015-6640?
CVE-2015-6640 affects Android versions 4.4.4, 5.0, 5.1.1, and all versions before 6.0.
Can CVE-2015-6640 lead to data loss?
Yes, CVE-2015-6640 can potentially lead to data loss due to vma list corruption.
Who is impacted by CVE-2015-6640?
Users of older Android versions prior to 6.0 are at risk of being impacted by CVE-2015-6640.

agent/references
agent/type
agent/first-publish-date
collector/nvd-index
agent/software-canonical-lookup-request
agent/softwarecombine
agent/author
agent/severity
agent/weakness
agent/description
collector/mitre-cve
source/MITRE
agent/tags
agent/event
agent/last-modified-date
collector/android-source
source/Android
agent/software-canonical-lookup
agent/source
vendor/google
canonical/google android
version/google android/4.4.4
version/google android/5.0
version/google android/5.1.1
version/google android/6.0

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.

Frequently Asked Questions

What is the severity of CVE-2015-6640?
CVE-2015-6640 has a high severity rating due to its potential to allow privilege escalation and denial of service.
How do I fix CVE-2015-6640?
To resolve CVE-2015-6640, you should update your Android device to version 6.0 or later.
What versions of Android are affected by CVE-2015-6640?
CVE-2015-6640 affects Android versions 4.4.4, 5.0, 5.1.1, and all versions before 6.0.
Can CVE-2015-6640 lead to data loss?
Yes, CVE-2015-6640 can potentially lead to data loss due to vma list corruption.
Who is impacted by CVE-2015-6640?
Users of older Android versions prior to 6.0 are at risk of being impacted by CVE-2015-6640.