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.
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.
Potential kernel crash (use-after-free) in the implementation of usermode helpers.
A race condition was discovered in the implementation of usermode helpers in the kernel. An attacker could exploit it from a container to cause a denial-of-service (kernel crash due to a use-after-free), or, potentially, to escalate their privileges in the system.
nf_tables: kernel crash in nf_tables_getset().
It was discovered that the implementation of nf_tables did not properly validate certain parameters. An attacker could exploit this from a container to cause a kernel crash: NULL pointer dereference or a general protection fault in nf_tables_getset().
nfnetlink: potential kernel crash (skb_over_panic) in skb_put().
It was discovered that nfnetlink subsystem did not properly validate certain messages. An attacker could exploit this from a container to cause a kernel crash: skb_over_panic in skb_put().
nf_conntrack: potential kernel crash in nf_ct_gre_keymap_destroy().
File system of a container becomes read-only, __ext4_handle_dirty_metadata() reports error 28.
Possible use-after-free error due to a race condition in cdev_get().
It was discovered that use-after-free condition was possible in cdev_get() if multiple processes simultaneously accessed a character device in a certain way. A local attacker could potentially exploit this to crash the kernel.
memcg: kernel crash in memcg_destroy_kmem_caches() caused by unbalanced css_tryget/css_put operations.
af_packet: potential soft lockup in case of certain errors when using TPACKET_V3.
It was found that if TPACKET_V3 was used and the kernel failed to obtain certain settings from a relevant network device, the retirement timer could be set incorrectly in the implementation AF_PACKET protocol. This could result in soft lockups and excessive CPU usage.
netlabel: kernel crash (null pointer dereference) while processing a specially crafted CIPSO packet.
A NULL pointer dereference was found in the implementation of SELinux. The issue occurs while importing the Commercial IP Security Option (CIPSO) protocol category bitmap into SELinux extensible bitmap. Parsing of a specially crafted CIPSO packet sent by a remote attacker could lead to a kernel crash (remote DoS).
Core dumps of some processes could contain uninitialized kernel data.
It was discovered that core dumps of userspace processes could contain copies of uninitialized kernel memory areas in certain cases. Although it is difficult for an attacker to control what data is in these areas, this issue, in theory, could be used to obtain sensitive information from the kernel.
crypto/authenc: kernel crash in crypto_ahash_setkey() when payload of a key is longer than 4 bytes and is not aligned.
An out-of-bounds read was found in the implementation of IPsec cryptographic algorithms ('authenc' module). When payload of a key was longer than 4 bytes but was not properly aligned, crypto_authenc_extractkeys() function could try to read data from a wrong location. This could lead to a kernel crash in crypto_ahash_setkey().
ploop: kernel crash (division by zero) in purge_lru_warn().
Denial of service by corrupting mountpoint reference counter.
It was discovered that a race condition was possible between pivot_root() and put_mountpoint() operations. A local unprivileged attacker could exploit this to corrupt mountpoint reference counter and cause a denial of service (kernel crash).
ext4: potential kernel crash in ext4_cross_rename(): certain error cases were not checked properly.
ext4: use-after-free when unmounting a corrupted file system with files that have no links.
futex: potential system hang due to a missing unlock operation in the error path of futex_wait_requeue_pi().
cbt: potential endless loops in the error paths.
netfilter: potential memory corruption caused by a helper from nf_conntrack_h323 module.
nf_conntrack: potential kernel crash in netlink_has_listeners().
ext4: attempts to freeze the FS could hang in certain cases due to an unbalanced internal write counter.
netlink: performance issues due to direct memory reclaim in netlink_dump() and netlink_trim().
memcg: kernel could crash when memory was uncharged from a cgroup while the cgroup was going offline.
It was found that a race was possible between uncharging memory from a cgroup and making that cgroup offline. This could lead to premature destruction of the cgroup and could cause a kernel crash.
packet: packet_sk_charge() could try to charge zero memory, leading to a use-after-free in memcg subsystem.
memcg: potential use-after-free in the implementation of uncharge operations.
qxl: kernel crash in qxl_release_fence_buffer_objects().
Use-after-free read in napi_gro_frags().
A flaw was found in the implementation of GRO, which allows an attacker with local access to trigger a use-after-free read in napi_gro_frags() and, potentially, crash the system.
i40iw: kernel complains about failed RTNL assertion in i40iw_addr_resolve_neigh().
Slow memory allocations in nf_conntrack when a netns is created.
When a new netns is created, high-order page allocations can happen in nf_ct_alloc_hashtable(). If memory is fragmented, such allocations can become very slow due to memory reclaim, etc. This, in turn, could result in significant slowdowns on the node.
nfsd: memory corruption in nfsd4_lock().
(enhancement) ploop: added interface to dump the cached BAT.
It was discovered that containers could get a broken on-disk BAT but have healthy in-kernel data in certain cases. To detect and fix such conditions, the means to dump the cached BAT were implemented in ploop. Note that, to make use of this enhancement, version 220.127.116.11 or newer of the userspace ploop tools is needed.
netfilter: kernel crash in the implementation of nf_tables due to use-after-free in dynamic operations.
A container with NFS server could force other such containers to use the older NFSv4 client tracker, which slows down NFS mounts.
mpt2sas: scheduling while atomic in _scsih_io_done().
ploop: potential corruption of the index during discard operation.
A race condition was discovered in ploop, which could lead to corruption of the index during discard operations in certain cases. Note. It is not recommended to manually unload the ReadyKernel patch with the fix for this issue while any discard operations for ploop images are in progress: the ploop images could be corrupted as a result. Upgrading the patch is OK, only manual unloads and downgrades can be problematic.
ploop: warn if a discard request is issued for the ploop header.
ve: detect removal of additional system libraries in the containers to simplify debugging.
Potential leak of a reference counter for a memory cgroup in memcg_expand_shrinker_maps().
Potential corruption of ploop images due to a race between the truncation thread and resize operations.
ve: make it easier to analyze removal of system libraries in the containers.
xfs: potential denial of service caused by missing unlock operation in xfs_setattr_nonsize().
It was discovered that xfs_setattr_nonsize() would not unlock 'ILOCK' lock if the user or group were out of their disk quota. As a result, any subsequent operation, which needed to take 'ILOCK', would get stuck, leading to a denial of service.
nf_tables: kernel crash in nft_rbtree_lookup().
ploop: holes in raw ploop images were handled incorrectly.
Kernel crash due to out-of-bounds memory accesses in process_vm_readv().
It was discovered that the implementation of process_vm_readv() system call could try to access memory outside of the structures it was processing in certain cases. A local unprivileged user could use this vulnerability to crash the system.
quotaoff operation executed in a container could get stuck in D state.
Certain operations with an empty ploop image could lead to its unexpected growth.
Incomplete fix for PSBM-100575: reading of /proc/bc/resources line by line would never end.
memcg: memory corruption caused by writing beyond the end of shrinker_map structure.
ixgbe: lots of warnings in the system log due to incorrect check for firmware errors.
ploop: kernel crashes when processing discard requests for ploop images in raw format.
scsi: printing lots of messages about rejected I/O causes a hard lockup and a kernel crash.
Kernel crash in shrink_slab() when trying to mount an image with a broken ext4 file system.
Reading of /proc/bc/resources line by line would never end: no end of file was reported.
Potential kernel crash in __radix_tree_insert() when fscache is used for NFS mounts.
sunrpc: potential kernel crash in bc_svc_process().
A bug in ploop prevented recovery of corrupted ploop images.
The minimum amount of reserved free memory (vm.min_free_kbytes) was set too high by default.
kvm: potential system hang due to an error in mmu_shrink_scan().
Processes could get stuck in copy_net_ns() forever.