-
PSBM-73001
sunrpc: potential kernel crash (use after free) in svc_process_common().
-
PSBM-87649
Potential out-of-bounds read in fuse_dev_splice_write().
-
PSBM-87670
Attempts to start a container fail with errors like 'cannot create directory /sys/fs/cgroup/beancounter/{something}'.
-
CVE-2017-18344
Out-of-bounds access in show_timer() function.
The implementation of timer_create system call in the Linux kernel before 4.14.8 doesn't properly validate the sigevent::sigev_notify field, which leads to out-of-bounds access in the show_timer function (called when /proc/$PID/timers is read). This allows userspace applications to read arbitrary kernel memory (on a kernel built with CONFIG_POSIX_TIMERS and CONFIG_CHECKPOINT_RESTORE).
https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2017-18344
-
CVE-2018-13405
SGID bit was not cleared on the files created by the users not present in the group that owned the SGID directory.
It was discovered that the local users could create files with an unintended group ownership and with group execution and SGID permission bits set. It was possible when a directory was SGID, belonged to a certain group and was writable by a user who was not a member of this group. This could lead to excessive permissions granted in case when they should not.
https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2018-13405
-
PSBM-86804
sctp: user-triggerable soft lockups.
A flaw was discovered in the implementation of SCTP protocol. A local unprivileged user could exploit it to cause soft lockups in the kernel (and, eventually, a denial of service) using specially crafted sequences of system calls.
-
PSBM-86790
Missing unlock_page() in the error path in fuse_readpages_fill().
-
PSBM-80743
Kernel warning in kill_block_super() when a mount operation fails.
-
PSBM-86511
The system could fail to restore a container with lots of mounts even if the number of mounts was within the limit.
It was discovered that the system could fail to restore a container ("VZctlError: Not enough system resources") if the container had more mounts than one third of the limit shown in /proc/sys/fs/ve-mount-nr.
-
PSBM-86420
Kernel crashes (NULL pointer dereference) if memory allocation fails in alloc_vfsmnt().
https://bugs.openvz.org/browse/OVZ-7039
-
CVE-2018-1120
Mapping a FUSE-backed file onto the command line arguments of a process causes denial of service.
By mapping a FUSE-backed file onto the memory area containing command line arguments or environment strings of a process, an attacker can cause any program that reads /proc/
/cmdline or /proc//environ for that process to block indefinitely or for a controlled amount of time. 'ps' and 'w' utilities are affected, among other things.
https://bugzilla.redhat.com/show_bug.cgi?id=1575472
-
PSBM-86093
Potential kernel crash (NULL pointer dereference) in ip6_route_dev_notify().
-
PSBM-85929
Potential kernel crash (NULL pointer dereference) in sysfs_readdir().
-
CVE-2018-5803
Kernel crash due to missing length check in _sctp_make_chunk() function.
It was found that _sctp_make_chunk() function did not check if the chunk length for INIT and INIT_ACK packets was within the allowed limits. A local attacker could exploit this to trigger a kernel crash.
https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2018-5803
-
PSBM-81731
Potential kernel crash in tcache_detach_page().
-
CVE-2018-1000199
ptrace: incorrect error handling leads to corruption and DoS.
The implementation of ptrace in the kernel does not handle errors correctly when working with the debug registers. As a result, the hardware breakpoints could become corrupted. An unprivileged user could exploit this flaw to crash the kernel resulting in a denial-of-service, or, potentially, to escalate their privileges in the system.
https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2018-1000199
-
CVE-2018-1087
KVM: error in exception handling leads to wrong debug stack.
A flaw was found in how KVM handled exceptions delivered after Mov SS or Pop SS instructions have encountered a breakpoint. As a result, exceptions passed to the guest kernel could have wrong values on the stack. An unprivileged KVM guest user could use this flaw to crash the guest kernel or, potentially, escalate their privileges in the guest system.
https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2018-1087
-
PSBM-84191
ip utility hangs in netlink_recvmsg().
It was discovered that the newer versions of ip utility (4.11.0, for example) may hang in netlink_recvmsg() when running on the kernel 3.10.0-693.21.1.vz7.46.7 and older. This was caused by mis-interpretation of netlink commands.
-
CVE-2017-17807
Missing permissions check for request_key() destination allows local attackers to add keys to keyring without write permission.
The KEYS subsystem omitted an access-control check when writing a key to the default keyring of the current task, allowing a local user to bypass security checks for the keyring. This compromised the validity of the keyring for those who relied on it.
https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2017-17807
-
CVE-2017-17450
System-wide OS fingerprint list was accessible to unprivileged users.
It was discovered that xt_osf_fingers data structure was accessible from any network namespace. This allowed unprivileged local users to bypass intended access restrictions and modify the system-wide OS fingerprint list used by specific iptables rules.
https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2017-17450
-
CVE-2017-17449
Netlink monitor created in a namespace could observe system-wide activity.
It was discovered that a nlmon link inside a child network namespace was not restricted to that namespace. An unprivilged local user could exploit that to monitor system-wide netlink activity.
https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2017-17449
-
CVE-2017-17448
Potential unprivileged access to the kernel structures used by netfilter conntrack helpers.
It was discovered that nfnl_cthelper_list structure was accessible to any user with CAP_NET_ADMIN capability in a network namespace. An unprivilged local user could exploit that to affect netfilter conntrack helpers on the host.
https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2017-17448
-
PSBM-83746
Kernel crash in move_freepages() due to incorrect BUG_ON() check.
It was discovered that the BUG_ON() check in move_freepages() did not verify that the relevant memory pages were valid. The kernel could crash as a result.
-
PSBM-83874
Kernel crash (stack overflow) caused by lots of internal mounts.
It was discovered that clone_mnt() did not clear MNT_INTERNAL flag for the internal mounts. As a result, the kernel could crash due to a stack overflow if lots of bind mounts of /proc/*/ns/* were created in a new namespace.
https://www.spinics.net/lists/netdev/msg496514.html
-
CVE-2018-1130
Kernel crash in dccp_write_xmit().
If "dccp_ipv6" module was loaded on the host, a local unprivileged user could trigger a kernel crash in dccp_write_xmit() or inet_csk_get_port() using a specially crafted sequence of system calls.
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=67f93df79aeefc3add4e4b31a752600f834236e2
-
PSBM-83474
Kernel crash in ip6mr_sk_done().
If the kernel failed to create an IPv6 socket, for example, due to cgroup.memsw limit, it would crash in ip6mr_sk_done() when trying to clean up multicast routes.
-
PSBM-81798
IPv6 routing tables incorrectly handled routing rules for throw routes.
It was discovered that IPv6 routing tables incorrectly handled routing rules for throw routes. This happened because errors were not propagated properly up to the fib_rules_lookup().
-
PSBM-82766
Container remained mounted in some cases after 'shutdown -h now' in it.
It was discovered that incorrect state of a container could be reported in /sys/fs/cgroup/ve/CTID/ve.state in some cases, which confused the user-space tools. As a result, a container could remain mounted after 'shutdown -h now' in it.
-
CVE-2018-1068
ebtables: out-of-bounds write via userland offsets in ebt_entry struct.
It was discovered that the implementation of ebtables in the kernel did not properly validate the offsets received from the user space. A local user with enough privileges in the user and network namespaces could use that to trigger an out-of-bounds write to the kernel address space.
https://bugzilla.redhat.com/show_bug.cgi?id=1552048
-
PSBM-82021
Potential kernel hang (lockup) during destruction of cgroups.
'memory' and 'memsw' counters could be overcharged when the limit of 'kmem' counter was reached. This would result in a kernel lockup during destruction of cgroups.
-
PSBM-81939
Potential kernel hang (endless loop) in try_charge().
-
PSBM-81600
Ploop: some IO requests were not marked as completed in case of errors.
-
PSBM-81488
High cpu usage in isolate_freepages_block().
vstorage-mount spent a lot of time in isolate_freepages_block() in some cases, causing performance issues.
-
PSBM-81509
Memcg swpin/swpout stats were calculated incorrectly.
-
PSBM-81264
Memory cgroups were not released when starting/stopping a container with Docker.
Memory cgroups were not correctly released during start/stop of a container with Docker. If the node had a significant amount of containers with Docker, this could lead to stopped containers not starting again.
-
PSBM-80340
Hard lockups happened when the kernel was processing SAK (Secure Attention Key).
-
PSBM-81033
Docker v17.11 and newer failed to start in a container.
Starting from v17.11, Docker checks is all cgroups are mounted and refuses to start if some cgroups are not. Some of Virtuozzo-specific cgroups were visible in the containers and were not mounted there, which prevented Docker from starting properly.
-
PSBM-81090
Kernel crash in mem_cgroup_iter().
-
PSBM-80839
Potential denial of service due to extensive memory consumption.
It was discovered that some operations with files in a container could lead to denial of service on the host due to extensive memory consumption.
-
CVE-2018-5344
loop: potential data race between open() and release() leading to use-after-free.
It was found that release() operation for the loop devices has insufficient protection for the device structures against the accesses from the concurrent open() operations. A local attacker can use specially arranged concurrent operations with a loop device to cause a denial of service (kernel crash due to a use-after-free error).
https://bugzilla.redhat.com/show_bug.cgi?id=1533909
-
CVE-2017-18017
netfilter: Use-after-free in tcpmss_mangle_packet().
If the system uses iptables and there are iptables rules with TCPMSS action there, a remote attacker may cause a denial of service (use-after-free in tcpmss_mangle_packet function leading to memory corruption) or possibly have unspecified other impact by sending specially crafted network packets.
https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2017-18017