Red Hat Security Advisory: kernel-rt security and bug fix update
🔗 CVE IDs covered (45)
📋 Description
CVE-2017-18551 — kernel: out of bounds write in function i2c_smbus_xfer_emulated in drivers/i2c/i2c-core-smbus.c CVE-2018-20836 — kernel: race condition in smp_task_timedout() and smp_task_done() in drivers/scsi/libsas/sas_expander.c leads to use-after-free CVE-2019-9454 — kernel: out of bounds write in i2c driver leads to local escalation of privilege CVE-2019-9458 — kernel: use after free due to race condition in the video driver leads to local privilege escalation CVE-2019-15217 — kernel: null pointer dereference in drivers/media/usb/zr364xx/zr364xx.c driver CVE-2019-15807 — kernel: Memory leak in drivers/scsi/libsas/sas_expander.c CVE-2019-15917 — kernel: use-after-free in drivers/bluetooth/hci_ldisc.c CVE-2019-16231 — kernel: null-pointer dereference in drivers/net/fjes/fjes_main.c CVE-2019-16233 — kernel: null pointer dereference in drivers/scsi/qla2xxx/qla_os.c CVE-2019-16994 — kernel: Memory leak in sit_init_net() in net/ipv6/sit.c CVE-2019-17053 — kernel: unprivileged users able to create RAW sockets in AF_IEEE802154 network protocol CVE-2019-17055 — kernel: unprivileged users able to create RAW sockets in AF_ISDN network protocol CVE-2019-18808 — kernel: memory leak in ccp_run_sha_cmd() function in drivers/crypto/ccp/ccp-ops.c CVE-2019-19046 — kernel: Denial Of Service in the __ipmi_bmc_register() function in drivers/char/ipmi/ipmi_msghandler.c CVE-2019-19055 — kernel: memory leak in the nl80211_get_ftm_responder_stats() function in net/wireless/nl80211.c allows DoS CVE-2019-19058 — kernel: A memory leak in the alloc_sgtable() function in drivers/net/wireless/intel/iwlwifi/fw/dbg.c allows for a DoS CVE-2019-19059 — kernel: Multiple memory leaks in the iwl_pcie_ctxt_info_gen3_init() function in drivers/net/wireless/intel/iwlwifi/pcie/ctxt-info-gen3.c allows for a DoS CVE-2019-19062 — kernel: memory leak in the crypto_report() function in crypto/crypto_user_base.c allows for DoS CVE-2019-19063 — kernel: Two memory leaks in the rtl_usb_probe() function in drivers/net/wireless/realtek/rtlwifi/usb.c allow for a DoS CVE-2019-19332 — Kernel: kvm: OOB memory write via kvm_dev_ioctl_get_cpuid CVE-2019-19447 — kernel: mounting a crafted ext4 filesystem image, performing some operations, and unmounting can lead to a use-after-free in ext4_put_super in fs/ext4/super.c CVE-2019-19523 — kernel: use-after-free caused by a malicious USB device in the drivers/usb/misc/adutux.c driver CVE-2019-19524 — kernel: a malicious USB device in the drivers/input/ff-memless.c leads to use-after-free CVE-2019-19530 — kernel: use-after-free caused by a malicious USB device in the drivers/usb/class/cdc-acm.c driver CVE-2019-19534 — kernel: information leak bug caused by a malicious USB device in the drivers/net/can/usb/peak_usb/pcan_usb_core.c driver CVE-2019-19537 — kernel: race condition caused by a malicious USB device in the USB character device driver layer CVE-2019-19767 — kernel: use-after-free in __ext4_expand_extra_isize and ext4_xattr_set_entry related to fs/ext4/inode.c and fs/ext4/super.c CVE-2019-19807 — kernel: use-after-free in sound/core/timer.c CVE-2019-20054 — kernel: Null pointer dereference in drop_sysctl_table() in fs/proc/proc_sysctl.c CVE-2019-20095 — kernel: memory leak in mwifiex_tm_cmd in drivers/net/wireless/marvell/mwifiex/cfg80211.c CVE-2019-20636 — kernel: out-of-bounds write via crafted keycode table CVE-2020-1749 — kernel: some ipv6 protocols not encrypted over ipsec tunnel CVE-2020-2732 — Kernel: kvm: nVMX: L2 guest may trick the L0 hypervisor to access sensitive L1 resources CVE-2020-8647 — kernel: out-of-bounds read in in vc_do_resize function in drivers/tty/vt/vt.c CVE-2020-8649 — kernel: invalid read location in vgacon_invert_region function in drivers/video/console/vgacon.c CVE-2020-9383 — kernel: out-of-bounds read in set_fdc in drivers/block/floppy.c CVE-2020-10690 — kernel: use-after-free in cdev_put() when a PTP device is removed while it's chardev is open CVE-2020-10732 — kernel: uninitialized kernel data leak in userspace coredumps CVE-2020-10742 — kernel: NFS client crash due to index buffer overflow during Direct IO write causing kernel panic CVE-2020-10751 — kernel: SELinux netlink permission check bypass CVE-2020-10942 — kernel: vhost-net: stack overflow in get_raw_socket while checking sk_family field CVE-2020-11565 — kernel: out-of-bounds write in mpol_parse_str function in mm/mempolicy.c CVE-2020-12770 — kernel: sg_write function lacks an sg_remove_request call in a certain failure case CVE-2020-12826 — kernel: possible to send arbitrary signals to a privileged (suidroot) parent process CVE-2020-14305 — kernel: memory corruption in Voice over IP nf_conntrack_h323 module
🎯 Affected products32
- Red Hat Enterprise Linux for Real Time (v. 7)
- Red Hat Enterprise Linux for Real Time for NFV (v. 7)
- kernel-rt-0:3.10.0-1160.rt56.1131.el7.src as a component of Red Hat Enterprise Linux for Real Time (v. 7)
- kernel-rt-0:3.10.0-1160.rt56.1131.el7.src as a component of Red Hat Enterprise Linux for Real Time for NFV (v. 7)
- kernel-rt-0:3.10.0-1160.rt56.1131.el7.x86_64 as a component of Red Hat Enterprise Linux for Real Time (v. 7)
- kernel-rt-0:3.10.0-1160.rt56.1131.el7.x86_64 as a component of Red Hat Enterprise Linux for Real Time for NFV (v. 7)
- kernel-rt-debug-0:3.10.0-1160.rt56.1131.el7.x86_64 as a component of Red Hat Enterprise Linux for Real Time (v. 7)
- kernel-rt-debug-0:3.10.0-1160.rt56.1131.el7.x86_64 as a component of Red Hat Enterprise Linux for Real Time for NFV (v. 7)
- kernel-rt-debug-debuginfo-0:3.10.0-1160.rt56.1131.el7.x86_64 as a component of Red Hat Enterprise Linux for Real Time (v. 7)
- kernel-rt-debug-debuginfo-0:3.10.0-1160.rt56.1131.el7.x86_64 as a component of Red Hat Enterprise Linux for Real Time for NFV (v. 7)
- kernel-rt-debug-devel-0:3.10.0-1160.rt56.1131.el7.x86_64 as a component of Red Hat Enterprise Linux for Real Time (v. 7)
- kernel-rt-debug-devel-0:3.10.0-1160.rt56.1131.el7.x86_64 as a component of Red Hat Enterprise Linux for Real Time for NFV (v. 7)
- kernel-rt-debug-kvm-0:3.10.0-1160.rt56.1131.el7.x86_64 as a component of Red Hat Enterprise Linux for Real Time for NFV (v. 7)
- kernel-rt-debug-kvm-debuginfo-0:3.10.0-1160.rt56.1131.el7.x86_64 as a component of Red Hat Enterprise Linux for Real Time for NFV (v. 7)
- kernel-rt-debuginfo-0:3.10.0-1160.rt56.1131.el7.x86_64 as a component of Red Hat Enterprise Linux for Real Time (v. 7)
- kernel-rt-debuginfo-0:3.10.0-1160.rt56.1131.el7.x86_64 as a component of Red Hat Enterprise Linux for Real Time for NFV (v. 7)
- kernel-rt-debuginfo-common-x86_64-0:3.10.0-1160.rt56.1131.el7.x86_64 as a component of Red Hat Enterprise Linux for Real Time (v. 7)
- kernel-rt-debuginfo-common-x86_64-0:3.10.0-1160.rt56.1131.el7.x86_64 as a component of Red Hat Enterprise Linux for Real Time for NFV (v. 7)
- kernel-rt-devel-0:3.10.0-1160.rt56.1131.el7.x86_64 as a component of Red Hat Enterprise Linux for Real Time (v. 7)
- kernel-rt-devel-0:3.10.0-1160.rt56.1131.el7.x86_64 as a component of Red Hat Enterprise Linux for Real Time for NFV (v. 7)
- kernel-rt-doc-0:3.10.0-1160.rt56.1131.el7.noarch as a component of Red Hat Enterprise Linux for Real Time (v. 7)
- kernel-rt-doc-0:3.10.0-1160.rt56.1131.el7.noarch as a component of Red Hat Enterprise Linux for Real Time for NFV (v. 7)
- kernel-rt-kvm-0:3.10.0-1160.rt56.1131.el7.x86_64 as a component of Red Hat Enterprise Linux for Real Time for NFV (v. 7)
- kernel-rt-kvm-debuginfo-0:3.10.0-1160.rt56.1131.el7.x86_64 as a component of Red Hat Enterprise Linux for Real Time for NFV (v. 7)
- kernel-rt-trace-0:3.10.0-1160.rt56.1131.el7.x86_64 as a component of Red Hat Enterprise Linux for Real Time (v. 7)
- kernel-rt-trace-0:3.10.0-1160.rt56.1131.el7.x86_64 as a component of Red Hat Enterprise Linux for Real Time for NFV (v. 7)
- kernel-rt-trace-debuginfo-0:3.10.0-1160.rt56.1131.el7.x86_64 as a component of Red Hat Enterprise Linux for Real Time (v. 7)
- kernel-rt-trace-debuginfo-0:3.10.0-1160.rt56.1131.el7.x86_64 as a component of Red Hat Enterprise Linux for Real Time for NFV (v. 7)
- kernel-rt-trace-devel-0:3.10.0-1160.rt56.1131.el7.x86_64 as a component of Red Hat Enterprise Linux for Real Time (v. 7)
- kernel-rt-trace-devel-0:3.10.0-1160.rt56.1131.el7.x86_64 as a component of Red Hat Enterprise Linux for Real Time for NFV (v. 7)
- +2 more not shown
✅ Remediation
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect. Workaround: Mitigation for this issue is either not available or the currently available options don't meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability. Workaround: To mitigate this issue, prevent modules v4l2-common, v4l2-dv-timings from being loaded if not being used for primary display. Please see https://access.redhat.com/solutions/41278 for how to blacklist a kernel module to prevent it from loading automatically. Workaround: To mitigate this issue, prevent module zr364xx from being loaded. Please see https://access.redhat.com/solutions/41278 for how to blacklist a kernel module to prevent it from loading automatically. Workaround: To mitigate this issue, prevent module hci_uart from being loaded. Please see https://access.redhat.com/solutions/41278 for how to blacklist a kernel module to prevent it from loading automatically. Workaround: At this time the only known way to 'mitigate' this flaw is to blacklist the kernel module from being loaded. Creating raw sockets with this protocol is a method of communicating with ISDN hardware, a technology that is becoming less and less common. Check https://access.redhat.com/solutions/41278 for instructions on how to disable the mISDN_core.ko module. Workaround: In order to mitigate this issue it is possible to prevent the affected code from being loaded by blacklisting the kernel module ccp. For instructions relating to how to blacklist a kernel module refer to: https://access.redhat.com/solutions/41278 Workaround: In order to mitigate this issue it is possible to prevent the affected code from being loaded by blacklisting the kernel module cfg80211. For instructions relating to how to blacklist a kernel module refer to: https://access.redhat.com/solutions/41278 . Workaround: In order to mitigate this issue it is possible to prevent the affected code from being loaded by blacklisting the kernel module iwlmvm. For instructions relating to how to blacklist a kernel module refer to: https://access.redhat.com/solutions/41278 . Workaround: In order to mitigate this issue it is possible to prevent the affected code from being loaded by blacklisting the kernel module iwlwifi. For instructions relating to how to blacklist a kernel module refer to: https://access.redhat.com/solutions/41278 . Workaround: In order to mitigate this issue it is possible to prevent the affected code from being loaded by blacklisting the kernel module crypto_user. For instructions relating to how to blacklist a kernel module refer to: https://access.redhat.com/solutions/41278 . Workaround: In order to mitigate this issue it is possible to prevent the affected code from being loaded by blacklisting the kernel module rtl8192cu. For instructions relating to how to blacklist a kernel module refer to: https://access.redhat.com/solutions/41278 . Workaround: Ext4 filesytems are built into the kernel so it is not possible to prevent the kernel module from loading. However, this flaw can be prevented by disallowing mounting of untrusted filesystems. As mounting is a privileged operation, (except for device hotplug) removing the ability for mounting and unmounting will prevent this flaw from being exploited. Workaround: As the system module will be auto-loaded when a device that uses the driver is attached (via USB), its use can be disabled by preventing the module from loading with the following instructions: # echo "install adutux /bin/true" >> /etc/modprobe.d/disable-adutux.conf The system will need to be restarted if the adutux module are loaded. In most circumstances, the kernel modules will be unable to be unloaded while any hardware is in use. If the system requires this module to work correctly, this mitigation may not be suitable. If you need further assistance, see KCS article https://access.redhat.com/solutions/41278 or contact Red Hat Global Support Services. Workaround: To mitigate this issue for the Red Hat Enterprise Linux 7 or higher version, prevent module ff-memless from being loaded. Please see https://access.redhat.com/solutions/41278 for how to blacklist a kernel module to prevent it from loading automatically. Workaround: As the devices module will be auto-loaded when the USB CAN bus adapter is connected, its can be disabled by preventing the module from loading with the following instructions: # echo "install peak_usb /bin/true" >> /etc/modprobe.d/disable-peak-usb-canbus.conf The system will need to be restarted if the peak_usb module is already loaded. In most circumstances, the kernel modules will be unable to be unloaded while any CAN bus interfaces are active and the protocol is in use. If the system requires this module to work correctly, this mitigation may not be suitable. If you need further assistance, see KCS article https://access.redhat.com/solutions/41278 or contact Red Hat Global Support Services. Workaround: Many Character devices can trigger this flaw as they leverage the lower levels of the USB subsystem. The safest method that I have found would be to disable USB ports that are able to be attacked using this method, disable them first by disallowing them from waking up from low-power states with the command (Replace X with the port number available). echo disabled >> /sys/bus/usb/devices/usbX/power/wakeup The system must also disable the specific ports power after with the command: echo suspend | sudo tee /sys/bus/usb/devices/usbX/power/level This change not persist through system reboots and must be applied at each reboot to be effective. Workaround: The mitigation is not to use debug_want_extra_isize parameter when mounting ext4 FS. Workaround: Red Hat has investigated whether a possible mitigation exists for this issue, and has not been able to identify a practical example. Please update as soon as possible. Workaround: As connecting to a wireless device is not automatic and initiated by a user, not connecting to rogue access points would prevent this flaw from being abused. Workaround: Disabling the IPV6 protocol may be a suitable workaround for systems that do not require the protocol to function correctly, however, if IPV6 is not in use this flaw will not be triggered. Workaround: The attack vector can be significantly reduced by preventing users from being able to log into the local virtual console. See the instructions on disabling local login here: https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/6/html/managing_smart_cards/pam_configuration_files , See the section on "pam_console" to deny users logging into the console. This mechanism should work from el6 forward to current versions of Red Hat Enterprise Linux. Workaround: Mitigation for this issue is to skip loading the affected floppy driver module onto the system till we have a fix available, this can be done by a blacklist mechanism, this will ensure the driver is not loaded at the boot time. ~~~ How do I blacklist a kernel module to prevent it from loading automatically? https://access.redhat.com/solutions/41278 ~~~ Workaround: Possible mitigation would be to disable core dumps system-wide by setting: * hard core 0 In the /etc/security/limits.conf file and restarting applications/services/processes which users may have access to or simply reboot the system. This disables core dumps which may not be a suitable workaround in your environment. Workaround: Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability. Workaround: A mitigation to this flaw would be to no longer use IPV6 on affected hardware …
🔗 References (52)
- selfhttps://access.redhat.com/errata/RHSA-2020:4062
- externalhttps://access.redhat.com/security/updates/classification/#important
- externalhttps://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/7.9_release_notes/index
- externalhttps://access.redhat.com/articles/5442481
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=1427551
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=1707796
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=1745528
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=1747216
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=1757368
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=1758242
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=1758248
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=1759681
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=1760100
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=1760310
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=1760420
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=1774988
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=1775015
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=1775021
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=1775042
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=1775047
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=1775074
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=1777418
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=1779594
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=1781679
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=1783434
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=1783459
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=1783518
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=1783540
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=1783561
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=1786078
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=1786160
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=1788009
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=1790063
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=1791954
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=1802555
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=1802563
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=1805135
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=1809833
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=1810685
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=1817141
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=1817718
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=1818818
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=1819377
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=1822077
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=1824059
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=1824918
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=1831399
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=1834845
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=1835127
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=1839634
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=1850716
- selfhttps://security.access.redhat.com/data/csaf/v2/advisories/2020/rhsa-2020_4062.json