CVE-2014-0206: Low severity Google Android vulnerability
Array index error in the aioreadeventsring function in fs/aio.c in the Linux kernel through 3.15.1 allows local users to obtain sensitive information from kernel memory via a large head value.
Other sources
It was found that aioreadeventsring() function in the Linux kernel's AIO subsystem did not properly sanitize AIO ring head coming from userspace.
An unprivileged local user could use this flaw to randomly disclose parts of (physical) memory belonging to kernel and/or other processes.
Introduced by: http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=a31ad380bed817aa25f8830ad23e1a0480fef797
Upstream commits: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=edfbbf388f29 https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=f8567a3845ac
Acknowledgements:
This issue was discovered by Mateusz Guzik of Red Hat.
— Red Hat
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2014-0206?
CVE-2014-0206 has been classified as a medium severity vulnerability due to its potential for information disclosure.
How do I fix CVE-2014-0206?
To fix CVE-2014-0206, update your Linux kernel to a version higher than 3.15.1 that includes the necessary patches.
Who is affected by CVE-2014-0206?
CVE-2014-0206 affects local users running the Linux kernel version 3.15.1 or earlier, including variants in Android.
What is the impact of CVE-2014-0206?
The impact of CVE-2014-0206 is that local users can potentially access sensitive kernel memory, leading to information disclosure.
Is CVE-2014-0206 still a risk if my system is updated?
If your system is updated to a kernel version above 3.15.1, the risk from CVE-2014-0206 is mitigated.