CVE-2014-0038: Linux Kernel Remote Memory Corruption Vulnerability
Linux - NewsThis forum is for original Linux News. If you'd like to write content for LQ, feel free to contact us.
All threads in the forum need to be approved before they will appear.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
The impact is a sort of arbitrary kernel write-where-what primitive by unprivileged users where the to-be-written area must contain valid timespec data initially (the first 64 bit long field must be positive
and the second one must be < 1G).
The bug was introduced by commit http://git.kernel.org/linus/ee4fa23c4b (other uses of COMPAT_USE_64BIT_TIME seem fine) and should affect all kernels since 3.4 (and perhaps vendor kernels if they backported x32 support along with this code). Note that CONFIG_X86_X32_ABI gets enabled at build time and only if CONFIG_X86_X32 is enabled and ld can build x32
Linux Kernel 'compat_sys_recvmmsg()' Function Remote Memory Corruption Vulnerability
The Linux Kernel is prone to a remote memory-corruption vulnerability.
A remote attacker can exploit this issue to execute arbitrary code with kernel privileges, corrupt the kernel memory, obtain sensitive information or crash the kernel; resulting in a denial-of-service condition.