ip_set: null pointer dereference in ip_set_utest().
It was discovered that an attacker could trigger a kernel crash (null pointer dereference) in ip_set_utest() by running a specially crafted sequence of system calls in a container.
ip_set: kernel crash in ip_set_comment_free().
It was discovered that an attacker could trigger a kernel crash (general protection fault) in ip_set_comment_free() by running a specially crafted sequence of system calls in a container.
xfrm subsystem of the Linux kernel could accept user-defined templates with invalid protocol numbers, which caused warnings in xfrm_state_fini().
If a subdirectory of a file system was exported via NFS, an attacker could use READDIRPLUS operation to access other parts of that file system.
Virtual machines could not start in certain cases due to incorrect detection of CPU feature 'IBPB'.
'Bad unlock balance' error in ipmr_mfc_seq_stop().
It was discovered that the implementation of IPv6 multicast routing could try to access wrong data when a user tried to read certain files in /proc. An attacker could exploit that from a container to trigger 'bad unlock balance' error in ipmr_mfc_seq_stop(), followed by a kernel crash.
Soft lockup in ext4_ext_find_extent().
It was discovered that certain ioctl operations in ext4 did not check their arguments properly. An attacker could exploit that from a container to trigger soft lockups in ext4_ext_find_extent() function, which could result in a denial of service.
Incorrect locking in TTY subsystem could lead to use-after-free conditions and cause memory corruption.
A specially crafted program running in a container could make certain processes on the host hang (denial of service).
Kernel crash in mem_cgroup_from_cont() due to a race between memory reclaim and offlining of a cgroup.
Kernel crash due to an incorrect BUG_ON() assertion in move_freepages().
ploop: certain operations with large ploop images could lead to a division by zero in __map_extent_bmap().
nfsd: Potential kernel crash in nfs4_put_stid().
'ploop grow' operation could fail in certain cases if the ploop image file contained holes.
Processes being killed by the OOM killer could continue consuming memory.
If a process running in a container performed large allocations of kernel memory, this could hit the memory limit for the container and trigger the OOM killer. It was discovered, however, that the process being killed by it could continue consuming memory for some time. This could lead to out of memory conditions on the host.
'ploop snapshot' operation could hang in certain cases.
bcache: Potential kernel crash when using RAID1 as a backing device.
ploop: Potential kernel crash or data corruption during backups due to racy operations with lockout data.
netfilter/ipset: excessive memory consumption leading to a denial of service.
If was discovered that not all memory allocated for ipset-related data was properly accounted for. An attacker could exploit it from a container to consume lots of kernel memory, making the host system unusable (denial of service).
NFS v4: potential memory corruption on the client system when processing security attributes.
It was discovered that a buffer overflow and memory corruption were possible if a system tried to mount an NFS v4 share where the files had security labels in the file attributes. An attacker would need to control the NFS server and make it send a specific series of responses to trigger the issue. The issue allows the attacker to crash the kernel on the client system or, potentially, escalate their privileges there.
netfilter: kernel crash due to a buffer overflow in ctnetlink_parse_tuple_filter().
It was discovered that a local attacker could pass a specially crafted configuration of conntrack to the kernel to cause a buffer overflow in ctnetlink_parse_tuple_filter() function. As a result, the kernel could crash.
The metadata validator in XFS may flag an inode with a valid extended attribute as corrupt.
A failure of the file system metadata validator in XFS can cause an inode with a valid, user-creatable extended attribute to be flagged as corrupt. This can lead to the filesystem being shutdown, or otherwise rendered inaccessible until it is remounted, leading to a denial of service.