RHSA-2020:5656: Moderate: kernel security update
The kernel packages contain the Linux kernel, the core of any Linux operating system.Security Fix(es): kernel: out of bounds write in function i2csmbusxferemulated in drivers/i2c/i2c-core-smbus.c (CVE-2017-18551) kernel: race condition in smptasktimedout() and smptaskdone() in drivers/scsi/libsas/sasexpander.c leads to use-after-free (CVE-2018-20836) kernel: out of bounds write in i2c driver leads to local escalation of privilege (CVE-2019-9454) kernel: Denial Of Service in the ipmibmcregister() function in drivers/char/ipmi/ipmimsghandler.c (CVE-2019-19046) kernel: mounting a crafted ext4 filesystem image, performing some operations, and unmounting can lead to a use-after-free in ext4putsuper in fs/ext4/super.c (CVE-2019-19447) kernel: out-of-bounds write via crafted keycode table (CVE-2019-20636) kernel: sgwrite function lacks an sgremoverequest call in a certain failure case (CVE-2020-12770) 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.
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of RHSA-2020:5656?
The severity of RHSA-2020:5656 is considered important due to potential security impacts.
How do I fix RHSA-2020:5656?
To fix RHSA-2020:5656, update the kernel packages to version 3.10.0-957.65.1.el7.
What vulnerabilities are addressed in RHSA-2020:5656?
RHSA-2020:5656 addresses vulnerabilities such as CVE-2017-18551 and a race condition in smp_task_timedout.
Which systems are affected by RHSA-2020:5656?
RHSA-2020:5656 affects Red Hat Enterprise Linux 7 systems with specific kernel packages.
Is a reboot required after applying RHSA-2020:5656?
Yes, a reboot is generally required to apply the updates related to RHSA-2020:5656.