Vulnerabilities > Linux > Linux Kernel > 3.18.47
| DATE | CVE | VULNERABILITY TITLE | RISK |
|---|---|---|---|
| 2016-05-02 | CVE-2015-4177 | Unspecified vulnerability in Linux Kernel The collect_mounts function in fs/namespace.c in the Linux kernel before 4.0.5 does not properly consider that it may execute after a path has been unmounted, which allows local users to cause a denial of service (system crash) by leveraging user-namespace root access for an MNT_DETACH umount2 system call. | 4.9 |
| 2016-05-02 | CVE-2015-4176 | Information Exposure vulnerability in Linux Kernel fs/namespace.c in the Linux kernel before 4.0.2 does not properly support mount connectivity, which allows local users to read arbitrary files by leveraging user-namespace root access for deletion of a file or directory. | 2.1 |
| 2016-05-02 | CVE-2015-2672 | Improper Input Validation vulnerability in Linux Kernel The xsave/xrstor implementation in arch/x86/include/asm/xsave.h in the Linux kernel before 3.19.2 creates certain .altinstr_replacement pointers and consequently does not provide any protection against instruction faulting, which allows local users to cause a denial of service (panic) by triggering a fault, as demonstrated by an unaligned memory operand or a non-canonical address memory operand. | 4.9 |
| 2016-05-02 | CVE-2015-1350 | Files or Directories Accessible to External Parties vulnerability in multiple products The VFS subsystem in the Linux kernel 3.x provides an incomplete set of requirements for setattr operations that underspecifies removing extended privilege attributes, which allows local users to cause a denial of service (capability stripping) via a failed invocation of a system call, as demonstrated by using chown to remove a capability from the ping or Wireshark dumpcap program. | 2.1 |
| 2016-05-02 | CVE-2014-9717 | Improper Access Control vulnerability in Linux Kernel fs/namespace.c in the Linux kernel before 4.0.2 processes MNT_DETACH umount2 system calls without verifying that the MNT_LOCKED flag is unset, which allows local users to bypass intended access restrictions and navigate to filesystem locations beneath a mount by calling umount2 within a user namespace. | 3.6 |
| 2016-04-27 | CVE-2016-3672 | 7PK - Security Features vulnerability in multiple products The arch_pick_mmap_layout function in arch/x86/mm/mmap.c in the Linux kernel through 4.5.2 does not properly randomize the legacy base address, which makes it easier for local users to defeat the intended restrictions on the ADDR_NO_RANDOMIZE flag, and bypass the ASLR protection mechanism for a setuid or setgid program, by disabling stack-consumption resource limits. | 7.8 |
| 2016-04-27 | CVE-2016-3156 | Resource Management Errors vulnerability in multiple products The IPv4 implementation in the Linux kernel before 4.5.2 mishandles destruction of device objects, which allows guest OS users to cause a denial of service (host OS networking outage) by arranging for a large number of IP addresses. | 5.5 |
| 2016-04-27 | CVE-2016-3134 | Improper Restriction of Operations within the Bounds of a Memory Buffer vulnerability in multiple products The netfilter subsystem in the Linux kernel through 4.5.2 does not validate certain offset fields, which allows local users to gain privileges or cause a denial of service (heap memory corruption) via an IPT_SO_SET_REPLACE setsockopt call. | 8.4 |
| 2016-04-27 | CVE-2016-2847 | Resource Management Errors vulnerability in multiple products fs/pipe.c in the Linux kernel before 4.5 does not limit the amount of unread data in pipes, which allows local users to cause a denial of service (memory consumption) by creating many pipes with non-default sizes. | 6.2 |
| 2016-04-27 | CVE-2016-2782 | NULL Pointer Dereference vulnerability in multiple products The treo_attach function in drivers/usb/serial/visor.c in the Linux kernel before 4.5 allows physically proximate attackers to cause a denial of service (NULL pointer dereference and system crash) or possibly have unspecified other impact by inserting a USB device that lacks a (1) bulk-in or (2) interrupt-in endpoint. | 4.9 |