- Kernel Update Version:
- Release Date:
- 2020-06-22 14:58:01
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).https://bugzilla.redhat.com/show_bug.cgi?id=1848652
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.https://bugzilla.kernel.org/show_bug.cgi?id=205433
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.CVE-2020-14305 was later assigned to this issue. See also: https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2020-14305.https://bugs.openvz.org/browse/OVZ-7188
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().
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().
Potential hard lockups in timer-related code: jiffies_lock could be held for a long time.
(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 18.104.22.168 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.
ext4: potential kernel crash (general protection fault) in ext4_free_blocks().
mpt2sas: scheduling while atomic in _scsih_io_done().