RHSA-2020:5437: Important: kernel security and bug fix update
The kernel packages contain the Linux kernel, the core of any Linux operating system.<br>Security Fix(es):<br><li> kernel: metadata validator in XFS may cause an inode with a valid, user-creatable extended attribute to be flagged as corrupt (CVE-2020-14385)</li> <li> kernel: The flowdissector feature allows device tracking (CVE-2019-18282)</li> <li> kernel: Buffer over-read in cryptoauthencextractkeys() when a payload longer than 4 bytes is not aligned. (CVE-2020-10769)</li> <li> kernel: buffer uses out of index in ext3/4 filesystem (CVE-2020-14314)</li> <li> kernel: umask not applied on filesystem without ACL support (CVE-2020-24394)</li> <li> kernel: TOCTOU mismatch in the NFS client code (CVE-2020-25212)</li> <li> kernel: improper input validation in pppcpparsecr function leads to memory corruption and read overflow (CVE-2020-25643)</li> 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.<br>Bug Fix(es):<br><li> WARNING in setrestoresigmask at ./arch/x86/include/asm/threadinfo.h:298 sigsuspend+0x6d/0x70 (BZ#1704650)</li> <li> [i40e] VFs see other VF's outgoing traffic (BZ#1845677)</li> <li> [Hyper-V][RHEL7] Two fixes for kdump over network (BZ#1846667)</li> <li> Loop in runtimers() because base->timerjiffies is very far behind causes a lockup condition. (BZ#1849716)</li> <li> XFS transaction overrun when running docker on VMWARE (overlay fs) (BZ#1857203)</li> <li> RHEL 7.9 NVMe/IB - Host crash encountered during array upgrade (BZ#1857397)</li> <li> False positive hard lockup detected while disabling the hard lockup detector via sysctl -w kernel.watchdog=0 (BZ#1860661)</li> <li> [Hyper-V][RHEL-7] Only notify Hyper-V for die events that are oops (BZ#1868130)</li> <li> Linux kernel crash due to openvswitch module (BZ#1869190)</li> <li> 'nodfs' option not working when using SMB2+ (BZ#1873033)</li> <li> RHEL7.7 zstream - ESS - kernel panic triggered by freelist pointer corruption (BZ#1873189)</li> <li> destroycfsbandwidth() is called by freefairschedgroup() without calling initcfsbandwidth() (BZ#1878000)</li> <li> NULL pointer at nvmerdmasetupctrl+0x1c2/0x8d0 [nvmerdma] when discover E5700 (BZ#1878950)</li> <li> IB Infiniband RDMA mlx5ib is freeing a kmalloc-512 cache that it does not own causing memory corruption. (BZ#1880184)</li> <li> [Azure][RHEL7] Two Patches Needed To Enable Azure Host Time-syncing in VMs (BZ#1884735)</li> <li> connect AFUNSPEC on a connecting AFINET6 socket returns an error (BZ#1886305)</li> <li> Rebuilding the grub with the CPU flag 'avx' disabled (clearcpuid=156) triggers kernel panic in xoravx2() (BZ#1886792)</li> <li> nfconntracksctp.h is not usable due to a missing commit (BZ#1887975)</li> <li> Starting pvmove on top of physical volumes on MD devices causes IO error on ongoing IO (BZ#1890059)</li>
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of RHSA-2020:5437?
The severity of RHSA-2020:5437 is classified as moderate.
How do I fix RHSA-2020:5437?
To fix RHSA-2020:5437, update the affected kernel packages to version 3.10.0-1160.11.1.el7 or later.
What specific vulnerabilities are addressed in RHSA-2020:5437?
RHSA-2020:5437 addresses vulnerabilities including CVE-2020-14385 related to metadata validation in XFS.
Which packages are affected in RHSA-2020:5437?
Affected packages in RHSA-2020:5437 include kernel, bpftool, and several related debugging and development packages.
What are the risks of not addressing RHSA-2020:5437?
Not addressing RHSA-2020:5437 may leave systems vulnerable to exploitation through the specific weaknesses in the kernel.