CVE-2015-1805: High severity Google Android vulnerability
A flaw was found in the way pipeiovcopyfromuser() and pipeiovcopytouser() functions handled iovecs remaining len accounting on failed atomic access.
An unprivileged local user could this flaw to crash the system or, potentially, escalate their privileges on the system.
Upstream fixes:
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=f0d1bec9d58d4c038d0ac958c9af82be6eb18045 http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=637b58c2887e5e57850865839cc75f59184b23d1
Acknowledgements:
The security impact of this issue was discovered by Red Hat.
Other sources
The (1) piperead and (2) pipewrite implementations in fs/pipe.c in the Linux kernel before 3.16 do not properly consider the side effects of failed copytouserinatomic and copyfromuserinatomic calls, which allows local users to cause a denial of service (system crash) or possibly gain privileges via a crafted application, aka an "I/O vector array overrun."
— Launchpad
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2015-1805?
CVE-2015-1805 is classified as a high severity vulnerability due to its potential to allow local privilege escalation or system crashes.
How do I fix CVE-2015-1805?
To fix CVE-2015-1805, upgrade to the patched versions of the Linux kernel or Android OS specified by the vendors.
Who is affected by CVE-2015-1805?
CVE-2015-1805 affects unprivileged local users on systems running vulnerable versions of the Linux kernel and specific versions of Android.
What types of systems are impacted by CVE-2015-1805?
CVE-2015-1805 impacts both Linux operating systems and Google Android versions 4.4.3 to 6.0.
Can CVE-2015-1805 lead to unauthorized access?
Yes, CVE-2015-1805 can potentially allow an attacker to escalate their privileges and gain unauthorized access to the system.