RHSA-2020:5418 — Security Advisory

An update for kernel is now available for Red Hat Enterprise Linux 8.2 Extended Update Support.

Red Hat Product Security has rated this update as having a security impact of Moderate. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available for each vulnerability from the CVE link(s) in the References section.

The kernel packages contain the Linux kernel, the core of any Linux operating system.

Security Fix(es):

• kernel: information exposure in drivers/char/random.c and kernel/time/timer.c (CVE-2020-16166)

For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

Bug Fix(es):

• [RHEL-8.3][arm64] CN99xx: DIMM errors not populated in EDAC sysfs (BZ#1857754)

• sctp: backports from upstream, 2nd phase (BZ#1878308)

• Backport upstream OVS performance patch fix (BZ#1879936)

• avoid flush_backlog IPI for isolated CPUs by configuring RPS cpumask (BZ#1883315)

• Unexpected fragmentation needed error, OpenShift 4, OVS, VXLAN, GSO, Azure (BZ#1885767)

• XFS: reflinked file data corruption (BZ#1886896)

• Scheduler: rq->tmp_alone_branch != &rq->leaf_cfs_rq_list (BZ#1890123)

• geneve: add transport ports in route lookup for geneve (BZ#1891819)

• BUG: using smp_processor_id() in preemptible [00000000] code: handler106/3082 (BZ#1893282)

• HRTICK not armed in specific cases with SCHED_DEADLINE (BZ#1894074)

• RHEL8.1 - ibmveth is producing TX errors over VXLAN when large send (TSO) is enabled (-> related to Red Hat bug 1816254 - OCP 4.3 - Authentication clusteroperator is in unknown state on POWER 9 servers") (BZ#1896300)

• RHEL8.2 - mm/gup: fix gup_fast with dynamic page table folding (BZ#1896352)

• block layer: update to upstream v5.8 (BZ#1896788)

• [Regression] RHEL8.2 zstream - Undetected Data corruption in MPI workloads that use VSX for reductions on POWER9 DD2.1 systems (BZ#1897279)

• ARO: excessive pod memory allocation causes node lockup (BZ#1901549)