- Kernel Update Version:
- Release Date:
- 2022-03-02 08:28:02
memcg: the limit on page cache (memory.cache.limit_in_bytes) could be exceeded significantly in certain cases.
File system of a container becomes read-only, __ext4_handle_dirty_metadata() reports error 28.https://forum.openvz.org/index.php?t=msg&th=13635
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.https://access.redhat.com/security/cve/cve-2020-0305
memcg: kernel crash in memcg_destroy_kmem_caches() caused by unbalanced css_tryget/css_put operations.
Hard lockup and kernel crash caused by incorrect locking in calc_load_ve().
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.https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2019-20812
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.https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2020-10732
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).https://bugzilla.redhat.com/show_bug.cgi?id=1848652
futex: potential system hang due to a missing unlock operation in the error path of futex_wait_requeue_pi().