ID

VAR-201805-0963

CVE

CVE-2018-3639

TITLE

CPU hardware utilizing speculative execution may be vulnerable to cache side-channel attacks

DESCRIPTION

Systems with microprocessors utilizing speculative execution and speculative execution of memory reads before the addresses of all prior memory writes are known may allow unauthorized disclosure of information to an attacker with local user access via a side-channel analysis, aka Speculative Store Bypass (SSB), Variant 4. CPU hardware utilizing speculative execution may be vulnerable to cache timing side-channel analysis. Two vulnerabilities are identified, known as "Variant 3a" and "Variant 4". CPUhardware is firmware that runs in the central processor for managing and controlling the CPU. Multiple CPUHardware information disclosure vulnerabilities. The vulnerability is caused by a race condition in the CPU cache processing. Local attackers can exploit vulnerabilities to obtain sensitive information through side channel analysis. AMD, ARM, and Intel CPUs are all CPU (central processing unit) products from different manufacturers. AMD, ARM, and Intel CPUs have security vulnerabilities. Relevant releases/architectures: RHV-M 4.2 - noarch 3. Description: The org.ovirt.engine-root is a core component of oVirt. Description: Kernel-based Virtual Machine (KVM) is a full virtualization solution for Linux on a variety of architectures. The qemu-kvm packages provide the user-space component for running virtual machines that use KVM. Once all virtual machines have shut down, start them again for this update to take effect. Bug Fix(es): * The "virsh capabilities" command previously displayed an inaccurate number of 4 KiB memory pages on systems with very large amounts of memory. This update optimizes the memory diagnostic mechanism to ensure memory page numbers are displayed correctly on such systems. (BZ#1582416) * After starting a large amount of guest virtual machines in a single session, the libvirtd service in some cases became unable to start any other guests until it was restarted. This update ensures that libvirtd properly frees memory used for D-Bus replies, which prevents the described problem from occurring. (BZ#1588390) 4. 7.2) - x86_64 3. Description: The libvirt library contains a C API for managing and interacting with the virtualization capabilities of Linux and other operating systems. In addition, libvirt provides tools for remote management of virtualized systems. For the stable distribution (stretch), these problems have been fixed in version 3.20180703.2~deb9u1. We recommend that you upgrade your intel-microcode packages. For the detailed security status of intel-microcode please refer to its security tracker page at: https://security-tracker.debian.org/tracker/intel-microcode Further information about Debian Security Advisories, how to apply these updates to your system and frequently asked questions can be found at: https://www.debian.org/security/ Mailing list: debian-security-announce@lists.debian.org -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEtuYvPRKsOElcDakFEMKTtsN8TjYFAlt11DsACgkQEMKTtsN8 TjaLRQ/7BRb1atQVGNSPWx7bSE1NTEGIv7MKLSQTBrAJt6VjsVoZPA/B4rgoxG8b li6UzUt0UfuEsS4H14O0fKqXHFWxeld1MjkEtMYaDbcaJ9PLUh2u3KxlEspmKhHG 2QTVwD88FZkeUgbGyfkI0w4n93UU7Kzm5FotKYiz1oRcdNgnCqpp+m/s9FpgWi00 np2DAYv6Qr4OixiT877pQS7vVJhp5QjFRysNb2FXHz9BagdpJgTpEid5tWkS50uy mABQefuajZuPXxhksR3d0BxCJErws9jnuXn7kd5P/Mv2lTpKgxTRkq8VzzhQRO1U TRn0p9Xg8g3lt+t8hdMGUsfwbbtX9kuOHwdT5QjURHhMN9BQSpk9jS6tqUF9tHXV Udbx6mYcRaBOjSBSDGs3VfH6PQEiHGMhXZWKWcJw3OlaUmLn147Mcj8OSIDJ8bIZ EYTiKtHJrZWAYmwWaeY1C8lfI7hUGPMpBbK8xXjTX5Iqjh8ibjYU6F5YnCFJ7N6t bFihXym3yapPOBZxE8BrDDX+tQ28juFU9qXjJ/VCc6Qpd6Y3aJXcnU+g7AUaYbGE SveoEMDPv4DeqA1wqc4ZJtc8T2E2fUHG8hhdWG24Os3zvjuiUg43UemIDgyoTL/A nL49y6Z/Jx6IxL+qiteaUJZzukel4ocGhOV9HAprahYjvV0v7Ps-aH -----END PGP SIGNATURE----- . (CVE-2018-3639) Note: This issue is present in hardware and cannot be fully fixed via software update. To be fully functional, up-to-date CPU microcode applied on the system is required. In this update mitigations for x86-64 architecture are provided. Here are the details from the Slackware 14.2 ChangeLog: +--------------------------+ patches/packages/linux-4.4.144/*: Upgraded. It also enables reporting on the Speculative Store Bypass vulnerability (aka GPZ Variant 4) which affects Intel processors and must be patched with a microcode update. To see the status of CPU vulnerability mitigations on your system, look at the files in: /sys/devices/system/cpu/vulnerabilities In addition, these kernels enable SMB2. Here's the complete list of kernel config changes from the previous 4.4.132: -X86_DEBUG_STATIC_CPU_HAS n CIFS_SMB2 n -> y +CC_OPTIMIZE_FOR_PERFORMANCE y +CIFS_SMB311 n +X86_FAST_FEATURE_TESTS y Be sure to upgrade your initrd after upgrading the kernel packages. If you use lilo to boot your machine, be sure lilo.conf points to the correct kernel and initrd and run lilo as root to update the bootloader. If you use elilo to boot your machine, you should run eliloconfig to copy the kernel and initrd to the EFI System Partition. For more information, see: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-3639 (* Security fix *) +--------------------------+ Where to find the new packages: +-----------------------------+ Thanks to the friendly folks at the OSU Open Source Lab (http://osuosl.org) for donating FTP and rsync hosting to the Slackware project! :-) Also see the "Get Slack" section on http://slackware.com for additional mirror sites near you. Updated packages for Slackware 14.2: ftp://ftp.slackware.com/pub/slackware/slackware-14.2/patches/packages/linux-4.4.144/kernel-firmware-20180727_b01151b-noarch-1.txz ftp://ftp.slackware.com/pub/slackware/slackware-14.2/patches/packages/linux-4.4.144/kernel-generic-4.4.144-i586-1.txz ftp://ftp.slackware.com/pub/slackware/slackware-14.2/patches/packages/linux-4.4.144/kernel-generic-smp-4.4.144_smp-i686-1.txz ftp://ftp.slackware.com/pub/slackware/slackware-14.2/patches/packages/linux-4.4.144/kernel-headers-4.4.144_smp-x86-1.txz ftp://ftp.slackware.com/pub/slackware/slackware-14.2/patches/packages/linux-4.4.144/kernel-huge-4.4.144-i586-1.txz ftp://ftp.slackware.com/pub/slackware/slackware-14.2/patches/packages/linux-4.4.144/kernel-huge-smp-4.4.144_smp-i686-1.txz ftp://ftp.slackware.com/pub/slackware/slackware-14.2/patches/packages/linux-4.4.144/kernel-modules-4.4.144-i586-1.txz ftp://ftp.slackware.com/pub/slackware/slackware-14.2/patches/packages/linux-4.4.144/kernel-modules-smp-4.4.144_smp-i686-1.txz ftp://ftp.slackware.com/pub/slackware/slackware-14.2/patches/packages/linux-4.4.144/kernel-source-4.4.144_smp-noarch-1.txz Updated packages for Slackware x86_64 14.2: ftp://ftp.slackware.com/pub/slackware/slackware64-14.2/patches/packages/linux-4.4.144/kernel-firmware-20180727_b01151b-noarch-1.txz ftp://ftp.slackware.com/pub/slackware/slackware64-14.2/patches/packages/linux-4.4.144/kernel-generic-4.4.144-x86_64-1.txz ftp://ftp.slackware.com/pub/slackware/slackware64-14.2/patches/packages/linux-4.4.144/kernel-headers-4.4.144-x86-1.txz ftp://ftp.slackware.com/pub/slackware/slackware64-14.2/patches/packages/linux-4.4.144/kernel-huge-4.4.144-x86_64-1.txz ftp://ftp.slackware.com/pub/slackware/slackware64-14.2/patches/packages/linux-4.4.144/kernel-modules-4.4.144-x86_64-1.txz ftp://ftp.slackware.com/pub/slackware/slackware64-14.2/patches/packages/linux-4.4.144/kernel-source-4.4.144-noarch-1.txz MD5 signatures: +-------------+ Slackware 14.2 packages: 78b4734f9898dceb88c85e2428ecb229 kernel-firmware-20180727_b01151b-noarch-1.txz c6d60676defaf0aff665e16d9c2a7fb5 kernel-generic-4.4.144-i586-1.txz cd9e3723a06cbc3f836ceda50568ee20 kernel-generic-smp-4.4.144_smp-i686-1.txz b3c43f455774ddd33247759baab252aa kernel-headers-4.4.144_smp-x86-1.txz cc87a7baeb407f080011625435a7e268 kernel-huge-4.4.144-i586-1.txz f081add71fe7909a49bc84becccc29ee kernel-huge-smp-4.4.144_smp-i686-1.txz 061a686e01ba27e94e67d0163f9fec7f kernel-modules-4.4.144-i586-1.txz d54f9e6eb5271d88bf80555f250cf742 kernel-modules-smp-4.4.144_smp-i686-1.txz 526b09e6aa33987cc1067dbfb418e414 kernel-source-4.4.144_smp-noarch-1.txz Slackware x86_64 14.2 packages: 78b4734f9898dceb88c85e2428ecb229 kernel-firmware-20180727_b01151b-noarch-1.txz ad06c7a0fdada92f42ec52759fe4f037 kernel-generic-4.4.144-x86_64-1.txz 411d9c7db2167177ee97a8f7cbf4366a kernel-headers-4.4.144-x86-1.txz f5176e27d85d80049532811423f8616b kernel-huge-4.4.144-x86_64-1.txz 847b5f06e3cd0eccce0a93b98412ede6 kernel-modules-4.4.144-x86_64-1.txz f8efe4ac11ac27114291238fafd7c406 kernel-source-4.4.144-noarch-1.txz Installation instructions: +------------------------+ Upgrade the packages as root: # upgradepkg kernel-*.txz If you are using an initrd, you'll need to rebuild it. For a 32-bit SMP machine, use this command (substitute the appropriate kernel version if you are not running Slackware 14.2): # /usr/share/mkinitrd/mkinitrd_command_generator.sh -k 4.4.144-smp | bash For a 64-bit machine, or a 32-bit uniprocessor machine, use this command (substitute the appropriate kernel version if you are not running Slackware 14.2): # /usr/share/mkinitrd/mkinitrd_command_generator.sh -k 4.4.144 | bash Please note that "uniprocessor" has to do with the kernel you are running, not with the CPU. Most systems should run the SMP kernel (if they can) regardless of the number of cores the CPU has. If you aren't sure which kernel you are running, run "uname -a". If you see SMP there, you are running the SMP kernel and should use the 4.4.144-smp version when running mkinitrd_command_generator. Note that this is only for 32-bit -- 64-bit systems should always use 4.4.144 as the version. If you are using lilo or elilo to boot the machine, you'll need to ensure that the machine is properly prepared before rebooting. If using LILO: By default, lilo.conf contains an image= line that references a symlink that always points to the correct kernel. No editing should be required unless your machine uses a custom lilo.conf. If that is the case, be sure that the image= line references the correct kernel file. Either way, you'll need to run "lilo" as root to reinstall the boot loader. If using elilo: Ensure that the /boot/vmlinuz symlink is pointing to the kernel you wish to use, and then run eliloconfig to update the EFI System Partition. +-----+ Slackware Linux Security Team http://slackware.com/gpg-key security@slackware.com +------------------------------------------------------------------------+ | To leave the slackware-security mailing list: | +------------------------------------------------------------------------+ | Send an email to majordomo@slackware.com with this text in the body of | | the email message: | | | | unsubscribe slackware-security | | | | You will get a confirmation message back containing instructions to | | complete the process. Please do not reply to this email address. -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 ==================================================================== Red Hat Security Advisory Synopsis: Important: kernel security and bug fix update Advisory ID: RHSA-2018:2161-01 Product: Red Hat Enterprise Linux Advisory URL: https://access.redhat.com/errata/RHSA-2018:2161 Issue date: 2018-07-10 CVE Names: CVE-2018-3639 ==================================================================== 1. Summary: An update for kernel is now available for Red Hat Enterprise Linux 7.3 Extended Update Support. Red Hat Product Security has rated this update as having a security impact of Important. 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. 2. Relevant releases/architectures: Red Hat Enterprise Linux ComputeNode EUS (v. 7.3) - noarch, x86_64 Red Hat Enterprise Linux ComputeNode Optional EUS (v. 7.3) - x86_64 Red Hat Enterprise Linux Server EUS (v. 7.3) - noarch, ppc64, ppc64le, s390x, x86_64 Red Hat Enterprise Linux Server Optional EUS (v. 7.3) - ppc64, ppc64le, x86_64 3. Description: The kernel packages contain the Linux kernel, the core of any Linux operating system. Security Fix(es): * An industry-wide issue was found in the way many modern microprocessor designs have implemented speculative execution of Load & Store instructions (a commonly used performance optimization). It relies on the presence of a precisely-defined instruction sequence in the privileged code as well as the fact that memory read from address to which a recent memory write has occurred may see an older value and subsequently cause an update into the microprocessor's data cache even for speculatively executed instructions that never actually commit (retire). As a result, an unprivileged attacker could use this flaw to read privileged memory by conducting targeted cache side-channel attacks. (CVE-2018-3639, x86 AMD) Red Hat would like to thank Ken Johnson (Microsoft Security Response Center) and Jann Horn (Google Project Zero) for reporting this issue. Bug Fix(es): * When a Nonvolatile Memory Express (NVMe) namespace was created, changed, or deleted, an occasional deadlock occurred. With this update, namespace scanning and removal does not hold a mutual exclusion (mutex) program object. As a result, a deadlock no longer occurs in the described scenario. (BZ#1566886) * Previously, a live migration of a virtual machine from one host with updated firmware to another host without updated firmware resulted in incorrect kernel settings for Meltdown mitigations, which could leave the kernel vulnerable to Meltdown. With this fix, the firmware on the new physical host is re-scanned for updates after a live migration. As a result, the kernel uses the correct mitigation in the described scenario. (BZ#1570507) * Previously, microcode updates on 32 and 64-bit AMD and Intel architectures were not synchronized. As a consequence, it was not possible to apply the microcode updates. This fix adds the synchronization to the microcode updates so that processors of the stated architectures receive updates at the same time. As a result, microcode updates are now synchronized. (BZ#1578044) * When switching from the indirect branch speculation (IBRS) feature to the retpolines feature, the IBRS state of some CPUs was sometimes not handled correctly. Consequently, some CPUs were left with the IBRS Model-Specific Register (MSR) bit set to 1, which could lead to performance issues. With this update, the underlying source code has been fixed to clear the IBRS MSR bits correctly, thus fixing the bug. (BZ#1586146) Users of kernel are advised to upgrade to these updated packages, which fix these bugs. The system must be rebooted for this update to take effect. 4. Solution: For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 5. Bugs fixed (https://bugzilla.redhat.com/): 1566890 - CVE-2018-3639 hw: cpu: speculative store bypass 6. Package List: Red Hat Enterprise Linux ComputeNode EUS (v. 7.3): Source: kernel-3.10.0-514.53.1.el7.src.rpm noarch: kernel-abi-whitelists-3.10.0-514.53.1.el7.noarch.rpm kernel-doc-3.10.0-514.53.1.el7.noarch.rpm x86_64: kernel-3.10.0-514.53.1.el7.x86_64.rpm kernel-debug-3.10.0-514.53.1.el7.x86_64.rpm kernel-debug-debuginfo-3.10.0-514.53.1.el7.x86_64.rpm kernel-debug-devel-3.10.0-514.53.1.el7.x86_64.rpm kernel-debuginfo-3.10.0-514.53.1.el7.x86_64.rpm kernel-debuginfo-common-x86_64-3.10.0-514.53.1.el7.x86_64.rpm kernel-devel-3.10.0-514.53.1.el7.x86_64.rpm kernel-headers-3.10.0-514.53.1.el7.x86_64.rpm kernel-tools-3.10.0-514.53.1.el7.x86_64.rpm kernel-tools-debuginfo-3.10.0-514.53.1.el7.x86_64.rpm kernel-tools-libs-3.10.0-514.53.1.el7.x86_64.rpm perf-3.10.0-514.53.1.el7.x86_64.rpm perf-debuginfo-3.10.0-514.53.1.el7.x86_64.rpm python-perf-3.10.0-514.53.1.el7.x86_64.rpm python-perf-debuginfo-3.10.0-514.53.1.el7.x86_64.rpm Red Hat Enterprise Linux ComputeNode Optional EUS (v. 7.3): x86_64: kernel-debug-debuginfo-3.10.0-514.53.1.el7.x86_64.rpm kernel-debuginfo-3.10.0-514.53.1.el7.x86_64.rpm kernel-debuginfo-common-x86_64-3.10.0-514.53.1.el7.x86_64.rpm kernel-tools-debuginfo-3.10.0-514.53.1.el7.x86_64.rpm kernel-tools-libs-devel-3.10.0-514.53.1.el7.x86_64.rpm perf-debuginfo-3.10.0-514.53.1.el7.x86_64.rpm python-perf-debuginfo-3.10.0-514.53.1.el7.x86_64.rpm Red Hat Enterprise Linux Server EUS (v. 7.3): Source: kernel-3.10.0-514.53.1.el7.src.rpm noarch: kernel-abi-whitelists-3.10.0-514.53.1.el7.noarch.rpm kernel-doc-3.10.0-514.53.1.el7.noarch.rpm ppc64: kernel-3.10.0-514.53.1.el7.ppc64.rpm kernel-bootwrapper-3.10.0-514.53.1.el7.ppc64.rpm kernel-debug-3.10.0-514.53.1.el7.ppc64.rpm kernel-debug-debuginfo-3.10.0-514.53.1.el7.ppc64.rpm kernel-debug-devel-3.10.0-514.53.1.el7.ppc64.rpm kernel-debuginfo-3.10.0-514.53.1.el7.ppc64.rpm kernel-debuginfo-common-ppc64-3.10.0-514.53.1.el7.ppc64.rpm kernel-devel-3.10.0-514.53.1.el7.ppc64.rpm kernel-headers-3.10.0-514.53.1.el7.ppc64.rpm kernel-tools-3.10.0-514.53.1.el7.ppc64.rpm kernel-tools-debuginfo-3.10.0-514.53.1.el7.ppc64.rpm kernel-tools-libs-3.10.0-514.53.1.el7.ppc64.rpm perf-3.10.0-514.53.1.el7.ppc64.rpm perf-debuginfo-3.10.0-514.53.1.el7.ppc64.rpm python-perf-3.10.0-514.53.1.el7.ppc64.rpm python-perf-debuginfo-3.10.0-514.53.1.el7.ppc64.rpm ppc64le: kernel-3.10.0-514.53.1.el7.ppc64le.rpm kernel-bootwrapper-3.10.0-514.53.1.el7.ppc64le.rpm kernel-debug-3.10.0-514.53.1.el7.ppc64le.rpm kernel-debug-debuginfo-3.10.0-514.53.1.el7.ppc64le.rpm kernel-debuginfo-3.10.0-514.53.1.el7.ppc64le.rpm kernel-debuginfo-common-ppc64le-3.10.0-514.53.1.el7.ppc64le.rpm kernel-devel-3.10.0-514.53.1.el7.ppc64le.rpm kernel-headers-3.10.0-514.53.1.el7.ppc64le.rpm kernel-tools-3.10.0-514.53.1.el7.ppc64le.rpm kernel-tools-debuginfo-3.10.0-514.53.1.el7.ppc64le.rpm kernel-tools-libs-3.10.0-514.53.1.el7.ppc64le.rpm perf-3.10.0-514.53.1.el7.ppc64le.rpm perf-debuginfo-3.10.0-514.53.1.el7.ppc64le.rpm python-perf-3.10.0-514.53.1.el7.ppc64le.rpm python-perf-debuginfo-3.10.0-514.53.1.el7.ppc64le.rpm s390x: kernel-3.10.0-514.53.1.el7.s390x.rpm kernel-debug-3.10.0-514.53.1.el7.s390x.rpm kernel-debug-debuginfo-3.10.0-514.53.1.el7.s390x.rpm kernel-debug-devel-3.10.0-514.53.1.el7.s390x.rpm kernel-debuginfo-3.10.0-514.53.1.el7.s390x.rpm kernel-debuginfo-common-s390x-3.10.0-514.53.1.el7.s390x.rpm kernel-devel-3.10.0-514.53.1.el7.s390x.rpm kernel-headers-3.10.0-514.53.1.el7.s390x.rpm kernel-kdump-3.10.0-514.53.1.el7.s390x.rpm kernel-kdump-debuginfo-3.10.0-514.53.1.el7.s390x.rpm kernel-kdump-devel-3.10.0-514.53.1.el7.s390x.rpm perf-3.10.0-514.53.1.el7.s390x.rpm perf-debuginfo-3.10.0-514.53.1.el7.s390x.rpm python-perf-3.10.0-514.53.1.el7.s390x.rpm python-perf-debuginfo-3.10.0-514.53.1.el7.s390x.rpm x86_64: kernel-3.10.0-514.53.1.el7.x86_64.rpm kernel-debug-3.10.0-514.53.1.el7.x86_64.rpm kernel-debug-debuginfo-3.10.0-514.53.1.el7.x86_64.rpm kernel-debug-devel-3.10.0-514.53.1.el7.x86_64.rpm kernel-debuginfo-3.10.0-514.53.1.el7.x86_64.rpm kernel-debuginfo-common-x86_64-3.10.0-514.53.1.el7.x86_64.rpm kernel-devel-3.10.0-514.53.1.el7.x86_64.rpm kernel-headers-3.10.0-514.53.1.el7.x86_64.rpm kernel-tools-3.10.0-514.53.1.el7.x86_64.rpm kernel-tools-debuginfo-3.10.0-514.53.1.el7.x86_64.rpm kernel-tools-libs-3.10.0-514.53.1.el7.x86_64.rpm perf-3.10.0-514.53.1.el7.x86_64.rpm perf-debuginfo-3.10.0-514.53.1.el7.x86_64.rpm python-perf-3.10.0-514.53.1.el7.x86_64.rpm python-perf-debuginfo-3.10.0-514.53.1.el7.x86_64.rpm Red Hat Enterprise Linux Server Optional EUS (v. 7.3): ppc64: kernel-debug-debuginfo-3.10.0-514.53.1.el7.ppc64.rpm kernel-debuginfo-3.10.0-514.53.1.el7.ppc64.rpm kernel-debuginfo-common-ppc64-3.10.0-514.53.1.el7.ppc64.rpm kernel-tools-debuginfo-3.10.0-514.53.1.el7.ppc64.rpm kernel-tools-libs-devel-3.10.0-514.53.1.el7.ppc64.rpm perf-debuginfo-3.10.0-514.53.1.el7.ppc64.rpm python-perf-debuginfo-3.10.0-514.53.1.el7.ppc64.rpm ppc64le: kernel-debug-debuginfo-3.10.0-514.53.1.el7.ppc64le.rpm kernel-debug-devel-3.10.0-514.53.1.el7.ppc64le.rpm kernel-debuginfo-3.10.0-514.53.1.el7.ppc64le.rpm kernel-debuginfo-common-ppc64le-3.10.0-514.53.1.el7.ppc64le.rpm kernel-tools-debuginfo-3.10.0-514.53.1.el7.ppc64le.rpm kernel-tools-libs-devel-3.10.0-514.53.1.el7.ppc64le.rpm perf-debuginfo-3.10.0-514.53.1.el7.ppc64le.rpm python-perf-debuginfo-3.10.0-514.53.1.el7.ppc64le.rpm x86_64: kernel-debug-debuginfo-3.10.0-514.53.1.el7.x86_64.rpm kernel-debuginfo-3.10.0-514.53.1.el7.x86_64.rpm kernel-debuginfo-common-x86_64-3.10.0-514.53.1.el7.x86_64.rpm kernel-tools-debuginfo-3.10.0-514.53.1.el7.x86_64.rpm kernel-tools-libs-devel-3.10.0-514.53.1.el7.x86_64.rpm perf-debuginfo-3.10.0-514.53.1.el7.x86_64.rpm python-perf-debuginfo-3.10.0-514.53.1.el7.x86_64.rpm These packages are GPG signed by Red Hat for security. Our key and details on how to verify the signature are available from https://access.redhat.com/security/team/key/ 7. References: https://access.redhat.com/security/cve/CVE-2018-3639 https://access.redhat.com/security/updates/classification/#important 8. Contact: The Red Hat security contact is <secalert@redhat.com>. More contact details at https://access.redhat.com/security/team/contact/ Copyright 2018 Red Hat, Inc. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIVAwUBW0Tt1NzjgjWX9erEAQjWjRAAqEnkLg83IXcDh/QVNDhAoM5gAh+OkfHJ LiuDz6CIHgDiv9K3BiG/dLNgL5caK11pxryqk/9kmtgoy6ClyqcrA2FNRIJMwugr PXTjAXNxekyn6gTX0I+8hSOulCZtkCRXmlUu79apvVT/eqQM6PfqjK02OjEL9uc8 59jO7ZoWcv7GVJhu+06QoHaWAqGHBOYL9ufCVAXZH6dY3aS2dPM4UUcZpVxsP8X/ HqXR/ciyXNPSQoGcR/waf/iZgx1pDIV6JXmdl/qlJXthohwa1ZwxD2qqEV3cM9uO XzXXVu9SD2D8cU4jClzIZ+XfM9J9dNl8j2YbZHaUs5IADNwqAIjPTb5leNhe6jqv omnbgOwkJ0mEOLeWBSpQhGxoq4rk4eUJLai1kcpw8MRa6RzOzTs+GHOxTpDfL681 S7F8GjN6J4l0gbW+fOkley3gdMi/74cZcWA6jX/GcjJrtzhlFhRsUDZqd8Eb+F/g quqdBLQ9Vc81FRlMoCATOhuqHM1/eJUcySbY3r1A6bU9oUQShN+prvIV4z5/ag6o WIPN2ImSDaSBACJoCSEby8e2jXs689JLHgPPS0QVvuMQK7wdYGu8/7W++L7+5/It IkS2XQFetG9urfkgM/OMVzeybOiGVsai+JAJOTxFnTWPeyIFF5MJ2E31Q11Amdlp YF80GD/Rvjo=ltf/ -----END PGP SIGNATURE----- -- RHSA-announce mailing list RHSA-announce@redhat.com https://www.redhat.com/mailman/listinfo/rhsa-announce . Description: The java-1.7.0-openjdk packages provide the OpenJDK 7 Java Runtime Environment and the OpenJDK 7 Java Software Development Kit. (CVE-2018-3639) Note: This is the OpenJDK side of the CVE-2018-3639 mitigation. 6.6) - noarch, x86_64 3. 7) - aarch64, noarch, ppc64le 3. (CVE-2018-3639, aarch64) * A flaw named SegmentSmack was found in the way the Linux kernel handled specially crafted TCP packets. A remote attacker could use this flaw to trigger time and calculation expensive calls to tcp_collapse_ofo_queue() and tcp_prune_ofo_queue() functions by sending specially modified packets within ongoing TCP sessions which could lead to a CPU saturation and hence a denial of service on the system. Maintaining the denial of service condition requires continuous two-way TCP sessions to a reachable open port, thus the attacks cannot be performed using spoofed IP addresses. (CVE-2018-5390) * A flaw named FragmentSmack was found in the way the Linux kernel handled reassembly of fragmented IPv4 and IPv6 packets. A remote attacker could use this flaw to trigger time and calculation expensive fragment reassembly algorithm by sending specially crafted packets which could lead to a CPU saturation and hence a denial of service on the system. (CVE-2018-5391) Space precludes documenting all of the security fixes in this advisory. See the descriptions of the remaining security fixes in the related Knowledge Article: https://access.redhat.com/articles/3658021 For more details about the security issue(s), including the impact, a CVSS score, and other related information, refer to the CVE page(s) listed in the References section. Bugs fixed (https://bugzilla.redhat.com/): 1516257 - CVE-2017-16648 kernel: Use-after-free in drivers/media/dvb-core/dvb_frontend.c 1528312 - CVE-2017-17805 kernel: Salsa20 encryption algorithm does not correctly handle zero-length inputs allowing local attackers to cause denial-of-service 1528323 - CVE-2017-17806 kernel: HMAC implementation does not validate that the underlying cryptographic hash algorithm is unkeyed allowing local attackers to cause denial-of-service 1533909 - CVE-2018-5344 kernel: drivers/block/loop.c mishandles lo_release serialization allowing denial-of-service 1539508 - CVE-2017-18075 kernel: Mishandled freeing of instances in pcrypt.c can allow a local user to cause a denial of service 1539706 - CVE-2018-5750 kernel: Kernel address information leak in drivers/acpi/sbshc.c:acpi_smbus_hc_add() function potentially allowing KASLR bypass 1541846 - CVE-2018-1000026 kernel: Improper validation in bnx2x network card driver can allow for denial of service attacks via crafted packet 1547824 - CVE-2018-1065 kernel: netfilter: xtables NULL pointer dereference in ip6_tables.c:ip6t_do_table() leading to a crash 1548412 - CVE-2017-13166 kernel: v4l2: disabled memory access protection mechanism allowing privilege escalation 1550142 - CVE-2018-7566 kernel: race condition in snd_seq_write() may lead to UAF or OOB-access 1551051 - CVE-2018-5803 kernel: Missing length check of payload in net/sctp/sm_make_chunk.c:_sctp_make_chunk() function allows denial of service 1551565 - CVE-2017-18208 kernel: Inifinite loop vulnerability in mm/madvise.c:madvise_willneed() function allows local denial of service 1552048 - CVE-2018-1068 kernel: Out-of-bounds write via userland offsets in ebt_entry struct in netfilter/ebtables.c 1553361 - CVE-2018-7757 kernel: Memory leak in the sas_smp_get_phy_events function in drivers/scsi/libsas/sas_expander.c 1560777 - CVE-2018-1092 kernel: NULL pointer dereference in ext4/mballoc.c:ext4_process_freed_data() when mounting crafted ext4 image 1560788 - CVE-2018-1094 kernel: NULL pointer dereference in ext4/xattr.c:ext4_xattr_inode_hash() causes crash with crafted ext4 image 1560793 - CVE-2018-1095 kernel: out-of-bound access in fs/posix_acl.c:get_acl() causes crash with crafted ext4 image 1566890 - CVE-2018-3639 hw: cpu: speculative store bypass 1568744 - CVE-2018-1000200 kernel: NULL pointer dereference on OOM kill of large mlocked process 1571062 - CVE-2018-8781 kernel: Integer overflow in drivers/gpu/drm/udl/udl_fb.c:udl_fb_mmap() can allow attackers to execute code in kernel space 1571623 - CVE-2018-10322 kernel: Invalid pointer dereference in xfs_ilock_attr_map_shared() when mounting crafted xfs image allowing denial of service 1573699 - CVE-2018-1118 kernel: vhost: Information disclosure in vhost/vhost.c:vhost_new_msg() 1575472 - CVE-2018-1120 kernel: fuse-backed file mmap-ed onto process cmdline arguments causes denial of service 1577408 - CVE-2018-10940 kernel: incorrect memory bounds check in drivers/cdrom/cdrom.c 1583210 - CVE-2018-11506 kernel: Stack-based buffer overflow in drivers/scsi/sr_ioctl.c allows denial of service or other unspecified impact 1589324 - CVE-2018-1000204 kernel: Infoleak caused by incorrect handling of the SG_IO ioctl 1590215 - CVE-2018-12232 kernel: NULL pointer dereference if close and fchownat system calls share a socket file descriptor 1590799 - CVE-2018-5848 kernel: buffer overflow in drivers/net/wireless/ath/wil6210/wmi.c:wmi_set_ie() may lead to memory corruption 1596795 - CVE-2018-10877 kernel: out-of-bound access in ext4_ext_drop_refs function with a crafted ext4 image 1596802 - CVE-2018-10878 kernel: out-of-bound write in ext4_init_block_bitmap function with a crafted ext4 image 1596806 - CVE-2018-10879 kernel: use-after-free detected in ext4_xattr_set_entry with a crafted file 1596812 - CVE-2018-10880 kernel: stack-out-of-bounds write in ext4_update_inline_data function 1596828 - CVE-2018-10881 kernel: out-of-bound access in ext4_get_group_info() when mounting and operating a crafted ext4 image 1596842 - CVE-2018-10882 kernel: stack-out-of-bounds write infs/jbd2/transaction.c 1596846 - CVE-2018-10883 kernel: stack-out-of-bounds write in jbd2_journal_dirty_metadata function 1599161 - CVE-2018-13405 kernel: Missing check in fs/inode.c:inode_init_owner() does not clear SGID bit on non-directories for non-members 1601704 - CVE-2018-5390 kernel: TCP segments with random offsets allow a remote denial of service (SegmentSmack) 1609664 - CVE-2018-5391 kernel: IP fragments with random offsets allow a remote denial of service (FragmentSmack) 1610958 - CVE-2017-18344 kernel: out-of-bounds access in the show_timer function in kernel/time/posix-timers.c 1622004 - CVE-2018-14619 kernel: crash (possible privesc) in kernel crypto api. 1623067 - CVE-2018-9363 kernel: Buffer overflow in hidp_process_report 1629636 - CVE-2018-14641 kernel: a bug in ip_frag_reasm() can cause a crash in ip_do_fragment() 6

IOT TAXONOMY

AFFECTED PRODUCTS