{"id":"MGASA-2015-0219","summary":"Updated kernel-tmb packages fix security vulnerabilities","details":"This kernel-tmb update is based on upstream -longterm 3.14.41 and fixes\nthe following security issues:\n\nIt was found that the Linux kernel's Infiniband subsystem did not properly\nsanitize input parameters while registering memory regions from user space\nvia the (u)verbs API. A local user with access to a /dev/infiniband/uverbsX\ndevice could use this flaw to crash the system or, potentially, escalate\ntheir privileges on the system (CVE-2014-8159)\n\nnet/netfilter/nf_conntrack_proto_generic.c in the Linux kernel before\n3.18 generates incorrect conntrack entries during handling of certain\niptables rule sets for the SCTP, DCCP, GRE, and UDP-Lite protocols,\nwhich allows remote attackers to bypass intended access restrictions\nvia packets with disallowed port numbers (CVE-2014-8160).\n\nThe em_sysenter function in arch/x86/kvm/emulate.c in the Linux kernel\nbefore 3.18.5, when the guest OS lacks SYSENTER MSR initialization,\nallows guest OS users to gain guest OS privileges or cause a denial of\nservice (guest OS crash) by triggering use of a 16-bit code segment for\nemulation of a SYSENTER instruction (CVE-2015-0239).\n\nThe stack randomization feature in the Linux kernel before 3.19.1 on 64-bit\nplatforms uses incorrect data types for the results of bitwise left-shift\noperations, which makes it easier for attackers to bypass the ASLR\nprotection mechanism by predicting the address of the top of the stack,\nrelated to the randomize_stack_top function in fs/binfmt_elf.c and the\nstack_maxrandom_size function in arch/x86/mm/mmap.c (CVE-2015-1593)\n\nXen 3.3.x through 4.5.x and the Linux kernel through 3.19.1 do not properly\nrestrict access to PCI command registers, which might allow local guest\nusers to cause a denial of service (non-maskable interrupt and host crash)\nby disabling the (1) memory or (2) I/O decoding for a PCI Express device\nand then accessing the device, which triggers an Unsupported Request\n(UR) response (CVE-2015-2150)\n\nSasha Levin discovered that the LLC subsystem exposed some variables as\nsysctls with the wrong type.  On a 64-bit kernel, this possibly allows\nprivilege escalation from a process with CAP_NET_ADMIN capability; it\nalso results in a trivial information leak (CVE-2015-2041).\n\nSasha Levin discovered that the RDS subsystem exposed some variables as\nsysctls with the wrong type.  On a 64-bit kernel, this results in a\ntrivial information leak (CVE-2015-2042).\n\nAndrew Lutomirski discovered that when a 64-bit task on an amd64 kernel\nmakes a fork(2) or clone(2) system call using int $0x80, the 32-bit\ncompatibility flag is set (correctly) but is not cleared on return.\nAs a result, both seccomp and audit will misinterpret the following\nsystem call by the task(s), possibly leading to a violation of security\npolicy (CVE-2015-2830).\n\nStephan Mueller discovered that the optimised implementation of RFC4106\nGCM for x86 processors that support AESNI miscalculated buffer addresses\nin some cases.  If an IPsec tunnel is configured to use this mode (also\nknown as AES-GCM-ESP) this can lead to memory corruption and crashes\n(even without malicious traffic).  This could potentially also result\nin remote code execution (CVE-2015-3331).\n\nBen Hutchings discovered that the TCP Fast Open feature regressed in\nLinux 3.16.7-ckt9, resulting in a kernel BUG when it is used.\nThis can be used as a local denial of service (CVE-2015-3332)\n\nIt was found that the Linux kernel's ping socket implementation didn't\nproperly handle socket unhashing during spurious disconnects which could\nlead to use-after-free flaw. On x86-64 architecture systems, a local user\nable to create ping sockets could use this flaw to crash the system. On\nnon-x86-64 architecture systems, a local user able to create ping sockets\ncould use this flaw to increase their privileges on the system.\nNote: By default ping sockets are disabled on the system \n(net.ipv4.ping_group_range = 1  0) and have to be explicitly enabled by the\nsystem administrator for specific user groups in order to exploit this issue\n(CVE-2015-3636).\n\nFor other fixes in this update, see the referenced changelogs.\n","modified":"2026-04-16T01:48:29.411033068Z","published":"2015-05-13T15:54:07Z","upstream":["CVE-2014-8159","CVE-2014-8160","CVE-2015-0239","CVE-2015-1593","CVE-2015-2041","CVE-2015-2042","CVE-2015-2150","CVE-2015-2830","CVE-2015-3331","CVE-2015-3332","CVE-2015-3636"],"references":[{"type":"ADVISORY","url":"https://advisories.mageia.org/MGASA-2015-0219.html"},{"type":"REPORT","url":"https://bugs.mageia.org/show_bug.cgi?id=15614"},{"type":"WEB","url":"https://www.kernel.org/pub/linux/kernel/v3.x/ChangeLog-3.14.33"},{"type":"WEB","url":"https://www.kernel.org/pub/linux/kernel/v3.x/ChangeLog-3.14.34"},{"type":"WEB","url":"https://www.kernel.org/pub/linux/kernel/v3.x/ChangeLog-3.14.35"},{"type":"WEB","url":"https://www.kernel.org/pub/linux/kernel/v3.x/ChangeLog-3.14.36"},{"type":"WEB","url":"https://www.kernel.org/pub/linux/kernel/v3.x/ChangeLog-3.14.37"},{"type":"WEB","url":"https://www.kernel.org/pub/linux/kernel/v3.x/ChangeLog-3.14.38"},{"type":"WEB","url":"https://www.kernel.org/pub/linux/kernel/v3.x/ChangeLog-3.14.39"},{"type":"WEB","url":"https://www.kernel.org/pub/linux/kernel/v3.x/ChangeLog-3.14.40"},{"type":"WEB","url":"https://www.kernel.org/pub/linux/kernel/v3.x/ChangeLog-3.14.41"}],"affected":[{"package":{"name":"kernel-tmb","ecosystem":"Mageia:4","purl":"pkg:rpm/mageia/kernel-tmb?arch=source&distro=mageia-4"},"ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.14.41-1.mga4"}]}],"ecosystem_specific":{"section":"core"},"database_specific":{"source":"https://advisories.mageia.org/MGASA-2015-0219.json"}}],"schema_version":"1.7.5","credits":[{"name":"Mageia","contact":["https://wiki.mageia.org/en/Packages_Security_Team"],"type":"COORDINATOR"}]}