readykernel-patch-163.46-124.0-1.vl7

Kernel Update Version:
3.10.0-1127.18.2.vz7.163.46
Release Date:
2021-03-12 06:47:02
  • PSBM-122965

    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.
  • PSBM-123063

    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.
  • PSBM-123084

    xfrm subsystem of the Linux kernel could accept user-defined templates with invalid protocol numbers, which caused warnings in xfrm_state_fini().

  • CVE-2021-20265

    Memory leak in the implementation of unix sockets.

    It was discovered that the implementation of unix sockets did not free certain data structures if a signal was received while unix_stream_recvmsg() function was running. An unprivileged local attacker could exploit this memory leak to cause a denial of service.
    https://access.redhat.com/security/cve/cve-2021-20265
  • CVE-2021-3178

    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.

    https://access.redhat.com/security/cve/cve-2021-3178
  • PSBM-124496

    pcompact would not compact ploop files if the underlying disk partitions had unusual alignment.

  • PSBM-126136

    Virtual machines could not start in certain cases due to incorrect detection of CPU feature 'IBPB'.

  • PSBM-126014

    The number of memory cgroups reached its limit because such cgroups were not deleted in certain cases.

    It was discovered that memory cgroups were not deleted in certain cases. Over time, the limit on the number of memory cgroups could be hit and new cgroups would not be created. As a result, containers could fail to start and would report 'Cannot allocate memory' errors, docker could fail to run in the containers too, etc.
  • PSBM-122990

    '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.
  • PSBM-122991

    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.
  • CVE-2020-29661

    Incorrect locking in TTY subsystem could lead to use-after-free conditions and cause memory corruption.

    https://access.redhat.com/security/cve/cve-2020-29661
  • PSBM-124581

    Userspace processes could crash with 'double free or corruption' errors due to a lost TLB flush in the kernel.

  • VSTOR-39656

    fuse_kio_pcs: Potential kernel crash in fuse_map_resolve().

  • PSBM-123043

    A specially crafted program running in a container could make certain processes on the host hang (denial of service).

  • PSBM-123085

    Kernel crash due to an incorrect BUG_ON() assertion in move_freepages().