Updated kernel packages fix security vulnerabilities
Publication date: 05 Aug 2014Modification date: 05 Aug 2014
Type: security
Affected Mageia releases : 4
CVE: CVE-2014-0206 , CVE-2014-4014 , CVE-2014-4171 , CVE-2014-4508 , CVE-2014-5045 , CVE-2014-5077
Description
This kernel update provides the upstream 3.12.25 longterm kernel and fixes the following security issues: Array index error in the aio_read_events_ring 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 (CVE-2014-0206). The capabilities implementation in the Linux kernel before 3.14.8 does not properly consider that namespaces are inapplicable to inodes, which allows local users to bypass intended chmod restrictions by first creating a user namespace, as demonstrated by setting the setgid bit on a file with group ownership of root (CVE-2014-4014) mm/shmem.c in the Linux kernel through 3.15.1 does not properly implement the interaction between range notification and hole punching, which allows local users to cause a denial of service (i_mutex hold) by using the mmap system call to access a hole, as demonstrated by interfering with intended shmem activity by blocking completion of (1) an MADV_REMOVE madvise call or (2) an FALLOC_FL_PUNCH_HOLE fallocate call (CVE-2014-4171). arch/x86/kernel/entry_32.S in the Linux kernel through 3.15.1 on 32-bit x86 platforms, when syscall auditing is enabled and the sep CPU feature flag is set, allows local users to cause a denial of service (OOPS and system crash) via an invalid syscall number, as demonstrated by number 1000 (CVE-2014-4508). A flaw was found in the way reference counting was handled in the Linux kernels VFS subsystem when unmount on symlink was performed. An unprivileged local user could use this flaw to cause OOM conditions leading to denial of service or, potentially, trigger use-after-free error (CVE-2014-5045). Linux kernel built with the support for Stream Control Transmission Protocol (CONFIG_IP_SCTP) is vulnerable to a NULL pointer dereference flaw. It could occur when simultaneous new connections are initiated between the same pair of hosts. A remote user/program could use this flaw to crash the system kernel resulting in DoS (CVE.2014-5077). For other fixes, see the referenced changelogs and the kernel changelog.
References
- https://bugs.mageia.org/show_bug.cgi?id=13801
- https://www.kernel.org/pub/linux/kernel/v3.x/ChangeLog-3.12.22
- https://www.kernel.org/pub/linux/kernel/v3.x/ChangeLog-3.12.23
- https://www.kernel.org/pub/linux/kernel/v3.x/ChangeLog-3.12.24
- https://www.kernel.org/pub/linux/kernel/v3.x/ChangeLog-3.12.25
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-0206
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-4014
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-4171
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-4508
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-5045
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-5077
SRPMS
4/nonfree
- kmod-broadcom-wl-6.30.223.141-35.mga4.nonfree
- kmod-fglrx-14.010.1006-5.mga4.nonfree
- kmod-nvidia173-173.14.39-20.mga4.nonfree
- kmod-nvidia304-304.119-15.mga4.nonfree
- kmod-nvidia-current-331.79-5.mga4.nonfree
4/core
- kernel-3.12.25-3.mga4
- kernel-userspace-headers-3.12.25-3.mga4
- kmod-vboxadditions-4.3.10-10.mga4
- kmod-virtualbox-4.3.10-10.mga4
- kmod-xtables-addons-2.3-50.mga4