CVE-2017-5754

Systems with microprocessors utilizing speculative execution and indirect branch prediction may allow unauthorized disclosure of information to an attacker with local user access via a side-channel analysis of the data cache.

Systems with microprocessors utilizing speculative execution and indirect branch prediction may allow unauthorized disclosure of information to an attacker with local user access via a side-channel analysis of the data cache.

This kernel update is based on the upstream 4.4.111 and fixes several security issues.

The most important fix in this update is for the security issue named "Meltdown" that is fixed in theese kernels by enabling kernel Page Table Isolation (KTPI). Note that according to AMD, this issue does not effect Amd processors, so it is not enabled by default on systems using Amd CPU.

The list of known security fixes and mitigations in this kernel:

kvm: vmx: Scrub hardware GPRs at VM-exit. This enables partial mitigation in kvm for the security issue named "Spectre" (CVE-2017-5715, CVE-2017-5753).

Systems with microprocessors utilizing speculative execution and indirect branch prediction may allow unauthorized disclosure of information to an attacker with local user access via a side-channel analysis of the data cache (CVE-2017-5754, "Meltdown").

A use-after-free vulnerability was found in network namespaces code affecting the Linux kernel before 4.14.11. The function get_net_ns_by_id() in net/core/net_namespace.c does not check for the net::count value after it has found a peer network in netns_ids idr, which could lead to double free and memory corruption. This vulnerability could allow an unprivileged local user to induce kernel memory corruption on the system, leading to a crash. Due to the nature of the flaw, privilege escalation cannot be fully ruled out, although it is thought to be unlikely (CVE-2017-15129).

The KVM implementation in the Linux kernel through 4.14.7 allows attackers to obtain potentially sensitive information from kernel memory, aka a write_mmio stack-based out-of-bounds read, related to arch/x86/kvm/x86.c and include/trace/events/kvm.h (CVE-2017-17741).

The Linux Kernel 2.6.32 and later are affected by a denial of service, by flooding the diagnostic port 0x80 an exception can be triggered leading to a kernel panic (CVE-2017-1000407).

The kernels are also fixed to allow loading cpu microcode for Amd family 17 (Zen) processors, and dracut have been fixed to properly support early firmware loading on the microcode on all Amd cpus.

For more info about Meltdown, Spectre and other fixes in this update, see the refences.

This kernel-tmb update is based on the upstream 4.4.111 and fixes several security issues.

The most important fix in this update is for the security issue named "Meltdown" that is fixed in theese kernels by enabling kernel Page Table Isolation (KTPI). Note that according to AMD, this issue does not effect Amd processors, so it is not enabled by default on systems using Amd CPU.

The list of known security fixes and mitigations in this kernel:

kvm: vmx: Scrub hardware GPRs at VM-exit. This enables partial mitigation in kvm for the security issue named "Spectre" (CVE-2017-5715, CVE-2017-5753).

Systems with microprocessors utilizing speculative execution and indirect branch prediction may allow unauthorized disclosure of information to an attacker with local user access via a side-channel analysis of the data cache (CVE-2017-5754, "Meltdown").

A use-after-free vulnerability was found in network namespaces code affecting the Linux kernel before 4.14.11. The function get_net_ns_by_id() in net/core/net_namespace.c does not check for the net::count value after it has found a peer network in netns_ids idr, which could lead to double free and memory corruption. This vulnerability could allow an unprivileged local user to induce kernel memory corruption on the system, leading to a crash. Due to the nature of the flaw, privilege escalation cannot be fully ruled out, although it is thought to be unlikely (CVE-2017-15129).

The KVM implementation in the Linux kernel through 4.14.7 allows attackers to obtain potentially sensitive information from kernel memory, aka a write_mmio stack-based out-of-bounds read, related to arch/x86/kvm/x86.c and include/trace/events/kvm.h (CVE-2017-17741).

The Linux Kernel 2.6.32 and later are affected by a denial of service, by flooding the diagnostic port 0x80 an exception can be triggered leading to a kernel panic (CVE-2017-1000407).

The kernels are also fixed to allow loading cpu microcode for Amd family 17 (Zen) processors.

For more info about Meltdown, Spectre and other fixes in this update, see the refences.

This kernel-linus update provides the upstream 4.4.111 and fixes several security issues.

The most important fix in this update is for the security issue named "Meltdown" that is fixed in theese kernels by enabling kernel Page Table Isolation (KTPI). Note that according to AMD, this issue does not effect Amd processors, so it is not enabled by default on systems using Amd CPU.

The list of known security fixes and mitigations in this kernel:

Systems with microprocessors utilizing speculative execution and indirect branch prediction may allow unauthorized disclosure of information to an attacker with local user access via a side-channel analysis of the data cache (CVE-2017-5754, "Meltdown").

A use-after-free vulnerability was found in network namespaces code affecting the Linux kernel before 4.14.11. The function get_net_ns_by_id() in net/core/net_namespace.c does not check for the net::count value after it has found a peer network in netns_ids idr, which could lead to double free and memory corruption. This vulnerability could allow an unprivileged local user to induce kernel memory corruption on the system, leading to a crash. Due to the nature of the flaw, privilege escalation cannot be fully ruled out, although it is thought to be unlikely (CVE-2017-15129).

The Linux Kernel 2.6.32 and later are affected by a denial of service, by flooding the diagnostic port 0x80 an exception can be triggered leading to a kernel panic (CVE-2017-1000407).

The kernels are also fixed to allow loading cpu microcode for Amd family 17 (Zen) processors.

For more info about Meltdown, Spectre and other fixes in this update, see the refences.

This kernel update is based on the upstream 4.14.13 and fixes several security issues.

The most important fix in this update is for the security issue named "Meltdown" that is fixed in theese kernels by enabling kernel Page Table Isolation (KPTI). Note that according to AMD, this issue does not effect Amd processors, so it is not enabled by default on systems using Amd CPU.

The list of known security fixes and mitigations in this kernel:

kvm: vmx: Scrub hardware GPRs at VM-exit. This enables partial mitigation in kvm for the security issue named "Spectre" (CVE-2017-5715, CVE-2017-5753).

Systems with microprocessors utilizing speculative execution and indirect branch prediction may allow unauthorized disclosure of information to an attacker with local user access via a side-channel analysis of the data cache (CVE-2017-5754, "Meltdown").

A use-after-free vulnerability was found in network namespaces code affecting the Linux kernel before 4.14.11. The function get_net_ns_by_id() in net/core/net_namespace.c does not check for the net::count value after it has found a peer network in netns_ids idr, which could lead to double free and memory corruption. This vulnerability could allow an unprivileged local user to induce kernel memory corruption on the system, leading to a crash. Due to the nature of the flaw, privilege escalation cannot be fully ruled out, although it is thought to be unlikely (CVE-2017-15129).

The KVM implementation in the Linux kernel through 4.14.7 allows attackers to obtain potentially sensitive information from kernel memory, aka a write_mmio stack-based out-of-bounds read, related to arch/x86/kvm/x86.c and include/trace/events/kvm.h (CVE-2017-17741).

The kernels are also fixed to allow loading cpu microcode for Amd family 17 (Zen) processors, and dracut have been fixed to properly support early firmware loading on the microcode on all Amd cpus.

For more info about Meltdown, Spectre and other fixes in this update, see the refences.

This kernel-tmb update is based on the upstream 4.14.13 and fixes several security issues.

The most important fix in this update is for the security issue named "Meltdown" that is fixed in theese kernels by enabling kernel Page Table Isolation (KTPI). Note that according to AMD, this issue does not effect Amd processors, so it is not enabled by default on systems using Amd CPU.

The list of known security fixes and mitigations in this kernel:

kvm: vmx: Scrub hardware GPRs at VM-exit. This enables partial mitigation in kvm for the security issue named "Spectre" (CVE-2017-5715, CVE-2017-5753).

Systems with microprocessors utilizing speculative execution and indirect branch prediction may allow unauthorized disclosure of information to an attacker with local user access via a side-channel analysis of the data cache (CVE-2017-5754, "Meltdown").

A use-after-free vulnerability was found in network namespaces code affecting the Linux kernel before 4.14.11. The function get_net_ns_by_id() in net/core/net_namespace.c does not check for the net::count value after it has found a peer network in netns_ids idr, which could lead to double free and memory corruption. This vulnerability could allow an unprivileged local user to induce kernel memory corruption on the system, leading to a crash. Due to the nature of the flaw, privilege escalation cannot be fully ruled out, although it is thought to be unlikely (CVE-2017-15129).

The KVM implementation in the Linux kernel through 4.14.7 allows attackers to obtain potentially sensitive information from kernel memory, aka a write_mmio stack-based out-of-bounds read, related to arch/x86/kvm/x86.c and include/trace/events/kvm.h (CVE-2017-17741).

The kernels are also fixed to allow loading cpu microcode for Amd family 17 (Zen) processors.

For more info about Meltdown, Spectre and other fixes in this update, see the refences.

This kernel-linus update provided the upstream 4.14.13 and fixes several security issues.

The most important fix in this update is for the security issue named "Meltdown" that is fixed in theese kernels by enabling kernel Page Table Isolation (KTPI). Note that according to AMD, this issue does not effect Amd processors, so it is not enabled by default on systems using Amd CPU.

The list of known security fixes and mitigations in this kernel:

Systems with microprocessors utilizing speculative execution and indirect branch prediction may allow unauthorized disclosure of information to an attacker with local user access via a side-channel analysis of the data cache (CVE-2017-5754, "Meltdown").

A use-after-free vulnerability was found in network namespaces code affecting the Linux kernel before 4.14.11. The function get_net_ns_by_id() in net/core/net_namespace.c does not check for the net::count value after it has found a peer network in netns_ids idr, which could lead to double free and memory corruption. This vulnerability could allow an unprivileged local user to induce kernel memory corruption on the system, leading to a crash. Due to the nature of the flaw, privilege escalation cannot be fully ruled out, although it is thought to be unlikely (CVE-2017-15129).

The kernels are also fixed to allow loading cpu microcode for Amd family 17 (Zen) processors.

For more info about Meltdown, Spectre and other fixes in this update, see the refences.

This update provides version 384.111 from the R384 branch, in order to help mitigate Spectre and Meltdown CPU security issues and keeps the driver working with security hardened kernels.

Note that so far, nVidia does believe that their GPUs are immune to the referenced security issues.

It also adds support for newer GPUs and fixes some bugs.

This kernel update is based on the upstream 4.14.20 and adds KPTI mitigation for Meltdown (CVE-2017-5754) on 32bit x86. Arm platorm has now also addedmitigations for Meltdown (CVE-2017-5754) and Spectre, variant 2 (CVE-2017-5715).

For other fixes in this update, read the referenced changelogs.

This kernel update is based on the upstream 4.14.25 and updates the KPTI mitigation for Meltdown (CVE-2017-5754) on 32bit x86. It also adds ome optimizations and improvements to mitigate some of the slowdons caused by the Meltdown (CVE-2017-5754) and Spectre, variant 2 (CVE-2017-5715).

Other security fixes in this update:

The netfilter subsystem in the Linux kernel through 4.15.7 mishandles the case of a rule blob that contains a jump but lacks a user-defined chain, which allows local users to cause a denial of service (NULL pointer dereference) by leveraging the CAP_NET_RAW or CAP_NET_ADMIN capability, related to arpt_do_table in net/ipv4/netfilter/arp_tables.c, ipt_do_table in net/ipv4/netfilter/ip_tables.c, and ip6t_do_table in net/ipv6/netfilter/ip6_tables.c (CVE-2018-1065).

Other changes in this update:

WireGuard has been updated to 0.0.20180304.

A fix in the scsi subsystem that prevents the kernel to hang or oops, triggered at least when trying to mount some raid6 setups (mga#22704).

input/goodix: add support for GDIX1002 (mga#22703)

For other upstream fixes in this update, read the referenced changelogs.

This kernel update is based on the upstream 4.14.30 and fixes at least the following security issues:

The KPTI mitigation for Meltdown (CVE-2017-5754) on 32bit x86 has been updated to revision 4.

A flaw was found in the Linux kernel implementation of 32 bit syscall interface for bridging allowing a privileged user to arbitrarily write to a limited range of kernel memory. This flaw can be exploited not only by a system's privileged user (a real "root" user), but also by an attacker who is a privileged user (a "root" user) in a user+network namespace (CVE-2018-1068).

A race condition vulnerability exists in the sound system, that can lead to a deadlock and denial of service condition (CVE-2018-1000004).

Other changes in this update:

3rdparty rtl8812au driver has been updated to v5.2.20 (mga#22808) and adds fixes for KRACK security issue.

For other upstream fixes in this update, read the referenced changelogs.

This kernel-tmb update is based on the upstream 4.14.44 and fixes at least the following security issues:

This update adds KPTI mitigation for Meltdown (CVE-2017-5754) on 32bit x86.

The netfilter subsystem in the Linux kernel through 4.15.7 mishandles the case of a rule blob that contains a jump but lacks a user-defined chain, which allows local users to cause a denial of service (NULL pointer dereference) by leveraging the CAP_NET_RAW or CAP_NET_ADMIN capability, related to arpt_do_table in net/ipv4/netfilter/arp_tables.c, ipt_do_table in net/ipv4/netfilter/ip_tables.c, and ip6t_do_table in net/ipv6/netfilter/ip6_tables.c (CVE-2018-1065).

A flaw was found in the Linux kernel implementation of 32 bit syscall interface for bridging allowing a privileged user to arbitrarily write to a limited range of kernel memory. This flaw can be exploited not only by a system's privileged user (a real "root" user), but also by an attacker who is a privileged user (a "root" user) in a user+network namespace (CVE-2018-1068).

On x86, MOV SS and POP SS behave strangely if they encounter a data breakpoint. If this occurs in a KVM guest, KVM incorrectly thinks that a #DB instruction was caused by the undocumented ICEBP instruction. This results in #DB being delivered to the guest kernel with an incorrect RIP on the stack. On most guest kernels, this will allow a guest user to DoS the guest kernel or even to escalate privilege to that of the guest kernel (CVE-2018-1087).

The ext4_iget function in fs/ext4/inode.c in the Linux kernel through 4.15.15 mishandles the case of a root directory with a zero i_links_count, which allows attackers to cause a denial of service (ext4_process_freed_data NULL pointer dereference and OOPS) via a crafted ext4 image (CVE-2018-1092).

The ext4_valid_block_bitmap function in fs/ext4/balloc.c in the Linux kernel through 4.15.15 allows attackers to cause a denial of service (out-of-bounds read and system crash) via a crafted ext4 image because balloc.c and ialloc.c do not validate bitmap block numbers (CVE-2018-1093).

The ext4_fill_super function in fs/ext4/super.c in the Linux kernel through 4.15.15 does not always initialize the crc32c checksum driver, which allows attackers to cause a denial of service (ext4_xattr_inode_hash NULL pointer dereference and system crash) via a crafted ext4 image (CVE-2018-1094).

The ext4_xattr_check_entries function in fs/ext4/xattr.c in the Linux kernel through 4.15.15 does not properly validate xattr sizes, which causes misinterpretation of a size as an error code, and consequently allows attackers to cause a denial of service (get_acl NULL pointer dereference and system crash) via a crafted ext4 image (CVE-2018-1095).

By mmap()ing a FUSE-backed file onto a process's memory containing command line arguments (or environment strings), an attacker can cause utilities from psutils or procps (such as ps, w) or any other program which makes a read() call to the /proc/<pid>/cmdline (or /proc/<pid>/environ) files to block indefinitely (denial of service) or for some controlled time (as a synchronization primitive for other attacks) (CVE-2018-1120).

A null pointer dereference in dccp_write_xmit() function in net/dccp/output.c in the Linux kernel before v4.16-rc7 allows a local user to cause a denial of service by a number of certain crafted system calls (CVE-2018-1130).

Speculative Store Bypass (SSB) – also known as Spectre Variant 4. 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 (CVE-2018-3639). NOTE! This fix only apply to Amd hardware so far as Intel CPUs need a fixed microcode update in order for the fix to get activated. At the time of this release we dont yet know when Intel will release new microcode.

The Linux kernel does not properly handle debug…

These are all security issues fixed in the kernel-devel-5.14.6-1.4 package on the GA media of openSUSE Tumbleweed.

These are all security issues fixed in the kernel-devel-longterm-6.6.17-1.1 package on the GA media of openSUSE Tumbleweed.

The SUSE Linux Enterprise 12 SP3 kernel was updated to receive various security and bugfixes.

This update adds mitigations for various side channel attacks against modern CPUs that could disclose content of otherwise unreadable memory (bnc#1068032).

• CVE-2017-5753 / 'SpectreAttack': Local attackers on systems with modern CPUs featuring deep instruction pipelining could use attacker controllable speculative execution over code patterns in the Linux Kernel to leak content from otherwise not readable memory in the same address space, allowing retrieval of passwords, cryptographic keys and other secrets.

  This problem is mitigated by adding speculative fencing on affected code paths throughout the Linux kernel.

• CVE-2017-5715 / 'SpectreAttack': Local attackers on systems with modern CPUs featuring branch prediction could use mispredicted branches to speculatively execute code patterns that in turn could be made to leak other non-readable content in the same address space, an attack similar to CVE-2017-5753.

  This problem is mitigated by disabling predictive branches, depending on CPU architecture either by firmware updates and/or fixes in the user-kernel privilege boundaries.

  Please also check with your CPU / Hardware vendor for available firmware or BIOS updates.

  As this feature can have a performance impact, it can be disabled using the 'nospec' kernel commandline option.

• CVE-2017-5754 / 'MeltdownAttack': Local attackers on systems with modern CPUs featuring deep instruction pipelining could use code patterns in userspace to speculative executive code that would read otherwise read protected memory.

  This problem is mitigated by unmapping the Linux Kernel from the user address space during user code execution, following a approach called 'KAISER'. The terms used here are 'KAISER' / 'Kernel Address Isolation' and 'PTI' / 'Page Table Isolation'.

  This is only enabled by default on affected architectures.

  This feature can be enabled / disabled by the 'pti=[on|off|auto]' or 'nopti' commandline options.

The following security bugs were fixed:

• CVE-2017-17806: The HMAC implementation (crypto/hmac.c) in the Linux kernel did not validate that the underlying cryptographic hash algorithm is unkeyed, allowing a local attacker able to use the AF_ALG-based hash interface (CONFIG_CRYPTO_USER_API_HASH) and the SHA-3 hash algorithm (CONFIG_CRYPTO_SHA3) to cause a kernel stack buffer overflow by executing a crafted sequence of system calls that encounter a missing SHA-3 initialization (bnc#1073874).
• CVE-2017-17805: The Salsa20 encryption algorithm in the Linux kernel did not correctly handle zero-length inputs, allowing a local attacker able to use the AF_ALG-based skcipher interface (CONFIG_CRYPTO_USER_API_SKCIPHER) to cause a denial of service (uninitialized-memory free and kernel crash) or have unspecified other impact by executing a crafted sequence of system calls that use the blkcipher_walk API. Both the generic implementation (crypto/salsa20_generic.c) and x86 implementation (arch/x86/crypto/salsa20_glue.c) of Salsa20 were vulnerable (bnc#1073792).

The following non-security bugs were fixed:

• Add undefine _unique_build_ids (bsc#964063)
• apei / ERST: Fix missing error handling in erst_reader() (bsc#1072556).
• arm: Hide finish_arch_post_lock_switch() from modules (bsc#1068032).
• autofs: fix careless error in recent commit (bnc#1012382 bsc#1065180).
• bnxt_en: Do not print 'Link speed -1 no longer supported' messages (bsc#1070116).
• bpf: prevent speculative execution in eBPF interpreter (bnc#1068032).
• carl9170: prevent speculative execution (bnc#1068032).
• ceph: drop negative child dentries before try pruning inode's alias (bsc#1073525).
• Check cmdline_find_option() retval properly and use boot_cpu_has().
• cifs: Fix NULL pointer deref on SMB2_tcon() failure (bsc#1071009).
• cw1200: prevent speculative execution (bnc#1068032). -…

The SUSE Linux Enterprise 11 SP4 kernel was updated to receive various security and bugfixes.

This update adds mitigations for various side channel attacks against modern CPUs that could disclose content of otherwise unreadable memory (bnc#1068032).

• CVE-2017-5753: Local attackers on systems with modern CPUs featuring deep instruction pipelining could use attacker controllable speculative execution over code patterns in the Linux Kernel to leak content from otherwise not readable memory in the same address space, allowing retrieval of passwords, cryptographic keys and other secrets.

  This problem is mitigated by adding speculative fencing on affected code paths throughout the Linux kernel.

  This issue is addressed for the x86_64, the IBM Power and IBM zSeries architecture.

• CVE-2017-5715: Local attackers on systems with modern CPUs featuring branch prediction could use mispredicted branches to speculatively execute code patterns that in turn could be made to leak other non-readable content in the same address space, an attack similar to CVE-2017-5753.

  This problem is mitigated by disabling predictive branches, depending on CPU architecture either by firmware updates and/or fixes in the user-kernel privilege boundaries.

  This is done with help of Linux Kernel fixes on the Intel/AMD x86_64 and IBM zSeries architectures. On x86_64, this requires also updates of the CPU microcode packages, delivered in seperate updates.

  For IBM Power and zSeries the required firmware updates are supplied over regular channels by IBM.

  As this feature can have a performance impact, it can be disabled using the 'nospec' kernel commandline option.

• CVE-2017-5754: Local attackers on systems with modern CPUs featuring deep instruction pipelining could use code patterns in userspace to speculative executive code that would read otherwise read protected memory, an attack similar to CVE-2017-5753.

  This problem is mitigated by unmapping the Linux Kernel from the user address space during user code execution, following a approach called 'KAISER'. The terms used here are 'KAISER' / 'Kernel Address Isolation' and 'PTI' / 'Page Table Isolation'.

  This update does this on the Intel x86_64 and IBM Power architecture. Updates are also necessary for the ARM architecture, but will be delivered in the next round of updates.

  This feature can be enabled / disabled by the 'pti=[on|off|auto]' or 'nopti' commandline options.

The following security bugs were fixed:

• CVE-2017-17806: The HMAC implementation (crypto/hmac.c) in the Linux kernel did not validate that the underlying cryptographic hash algorithm is unkeyed, allowing a local attacker able to use the AF_ALG-based hash interface (CONFIG_CRYPTO_USER_API_HASH) and the SHA-3 hash algorithm (CONFIG_CRYPTO_SHA3) to cause a kernel stack buffer overflow by executing a crafted sequence of system calls that encounter a missing SHA-3 initialization (bnc#1073874).
• CVE-2017-17805: The Salsa20 encryption algorithm in the Linux kernel did not correctly handle zero-length inputs, allowing a local attacker able to use the AF_ALG-based skcipher interface (CONFIG_CRYPTO_USER_API_SKCIPHER) to cause a denial of service (uninitialized-memory free and kernel crash) or have unspecified other impact by executing a crafted sequence of system calls that use the blkcipher_walk API. Both the generic implementation (crypto/salsa20_generic.c) and x86 implementation (arch/x86/crypto/salsa20_glue.c) of Salsa20 were vulnerable (bnc#1073792).
• CVE-2017-15868: The bnep_add_connection function in net/bluetooth/bnep/core.c in the Linux kernel did not ensure that an l2cap socket is available, which allowed local users to gain privileges via a crafted application (bnc#1071470).
• CVE-2017-13167: An elevation of privilege vulnerability in the kernel sound timer. (bnc#1072876).
• CVE-2017-16538: drivers/media/usb/dvb-usb-v2/lmedm04.c in the Linux kernel allowed local…

The SUSE Linux Enterprise 12 SP2 kernel was updated to receive various security and bugfixes.

This update adds mitigations for various side channel attacks against modern CPUs that could disclose content of otherwise unreadable memory (bnc#1068032).

• CVE-2017-5753 / 'SpecŧreAttack': Local attackers on systems with modern CPUs featuring deep instruction pipelining could use attacker controllable speculative execution over code patterns in the Linux Kernel to leak content from otherwise not readable memory in the same address space, allowing retrieval of passwords, cryptographic keys and other secrets.

  This problem is mitigated by adding speculative fencing on affected code paths throughout the Linux kernel.

• CVE-2017-5715 / 'SpectreAttack': Local attackers on systems with modern CPUs featuring branch prediction could use mispredicted branches to speculatively execute code patterns that in turn could be made to leak other non-readable content in the same address space, an attack similar to CVE-2017-5753.

  This problem is mitigated by disabling predictive branches, depending on CPU architecture either by firmware updates and/or fixes in the user-kernel privilege boundaries.

  Please also check with your CPU / Hardware vendor on updated firmware or BIOS images regarding this issue.

  As this feature can have a performance impact, it can be disabled using the 'nospec' kernel commandline option.

• CVE-2017-5754 / 'MeltdownAttack': Local attackers on systems with modern CPUs featuring deep instruction pipelining could use code patterns in userspace to speculative executive code that would read otherwise read protected memory, an attack similar to CVE-2017-5753.

  This problem is mitigated by unmapping the Linux Kernel from the user address space during user code execution, following a approach called 'KAISER'. The terms used here are 'KAISER' / 'Kernel Address Isolation' and 'PTI' / 'Page Table Isolation'.

  Note that this is only done on affected platforms.

  This feature can be enabled / disabled by the 'pti=[on|off|auto]' or 'nopti' commandline options.

Also the following unrelated security bugs were fixed:

• CVE-2017-17806: The HMAC implementation (crypto/hmac.c) in the Linux kernel did not validate that the underlying cryptographic hash algorithm is unkeyed, allowing a local attacker able to use the AF_ALG-based hash interface (CONFIG_CRYPTO_USER_API_HASH) and the SHA-3 hash algorithm (CONFIG_CRYPTO_SHA3) to cause a kernel stack buffer overflow by executing a crafted sequence of system calls that encounter a missing SHA-3 initialization (bnc#1073874).
• CVE-2017-17805: The Salsa20 encryption algorithm in the Linux kernel did not correctly handle zero-length inputs, allowing a local attacker able to use the AF_ALG-based skcipher interface (CONFIG_CRYPTO_USER_API_SKCIPHER) to cause a denial of service (uninitialized-memory free and kernel crash) or have unspecified other impact by executing a crafted sequence of system calls that use the blkcipher_walk API. Both the generic implementation (crypto/salsa20_generic.c) and x86 implementation (arch/x86/crypto/salsa20_glue.c) of Salsa20 were vulnerable (bnc#1073792).

The following non-security bugs were fixed:

• Add undefine _unique_build_ids (bsc#964063)
• Always sign validate_negotiate_info reqs (bsc#1071009, fate#324404).
• apei / ERST: Fix missing error handling in erst_reader() (bsc#1072556).
• arm: Hide finish_arch_post_lock_switch() from modules (bsc#1068032).
• autofs: fix careless error in recent commit (bnc#1012382 bsc#1065180).
• bpf: prevent speculative execution in eBPF interpreter (bnc#1068032).
• carl9170: prevent speculative execution (bnc#1068032).
• Check cmdline_find_option() retval properly and use boot_cpu_has().
• cw1200: prevent speculative execution (bnc#1068032).
• e1000e: Avoid receiver overrun interrupt bursts (bsc#969470 FATE#319819).
• e1000e: Fix e1000_check_for_copper_link_ich8lan return…

The SUSE Linux Enterprise 12 SP1 LTSS kernel was updated to receive various security and bugfixes.

This update adds mitigations for various side channel attacks against modern CPUs that could disclose content of otherwise unreadable memory (bnc#1068032).

• CVE-2017-5753 / 'SpectreAttack': Local attackers on systems with modern CPUs featuring deep instruction pipelining could use attacker controllable speculative execution over code patterns in the Linux Kernel to leak content from otherwise not readable memory in the same address space, allowing retrieval of passwords, cryptographic keys and other secrets.

  This problem is mitigated by adding speculative fencing on affected code paths throughout the Linux kernel.

  This issue is addressed for the x86_64, IBM Power and IBM zSeries architecture.

• CVE-2017-5715 / 'SpectreAttack': Local attackers on systems with modern CPUs featuring branch prediction could use mispredicted branches to speculatively execute code patterns that in turn could be made to leak other non-readable content in the same address space, an attack similar to CVE-2017-5753.

  This problem is mitigated by disabling predictive branches, depending on CPU architecture either by firmware updates and/or fixes in the user-kernel privilege boundaries.

  This is done with help of Linux Kernel fixes on the Intel/AMD x86_64 and IBM zSeries architectures. On x86_64, this requires also updates of the CPU microcode packages, delivered in seperate updates.

  For IBM Power and zSeries the required firmware updates are supplied over regular channels by IBM.

  As this feature can have a performance impact, it can be disabled using the 'nospec' kernel commandline option.

• CVE-2017-5754 / 'MeltdownAttack': Local attackers on systems with modern CPUs featuring deep instruction pipelining could use code patterns in userspace to speculative executive code that would read otherwise read protected memory, an attack similar to CVE-2017-5753.

  This problem is mitigated by unmapping the Linux Kernel from the user address space during user code execution, following a approach called 'KAISER'. The terms used here are 'KAISER' / 'Kernel Address Isolation' and 'PTI' / 'Page Table Isolation'.

  This update does this on the x86_64 architecture, it is not required on the IBM zSeries architecture.

  This feature can be enabled / disabled by the 'pti=[on|off|auto]' or 'nopti' commandline options.

The following security bugs were fixed:

• CVE-2017-15868: The bnep_add_connection function in net/bluetooth/bnep/core.c in the Linux kernel did not ensure that an l2cap socket is available, which allowed local users to gain privileges via a crafted application (bnc#1071470).
• CVE-2017-13167: An elevation of privilege vulnerability in the kernel sound timer. (bnc#1072876).
• CVE-2017-16538: drivers/media/usb/dvb-usb-v2/lmedm04.c in the Linux kernel allowed local users to cause a denial of service (general protection fault and system crash) or possibly have unspecified other impact via a crafted USB device, related to a missing warm-start check and incorrect attach timing (dm04_lme2510_frontend_attach versus dm04_lme2510_tuner) (bnc#1066569).
• CVE-2017-17558: The usb_destroy_configuration function in drivers/usb/core/config.c in the USB core subsystem in the Linux kernel did not consider the maximum number of configurations and interfaces before attempting to release resources, which allowed local users to cause a denial of service (out-of-bounds write access) or possibly have unspecified other impact via a crafted USB device (bnc#1072561).
• CVE-2017-17450: net/netfilter/xt_osf.c in the Linux kernel did not require the CAP_NET_ADMIN capability for add_callback and remove_callback operations, which allowed local users to bypass intended access restrictions because the xt_osf_fingers data structure is shared across all net namespaces (bnc#1071695).
• CVE-2017-17449: The…

The SUSE Linux Enterprise 11 SP3 LTSS kernel was updated to receive various security and bugfixes.

This update adds mitigations for various side channel attacks against modern CPUs that could disclose content of otherwise unreadable memory (bnc#1068032).

• CVE-2017-5753: Local attackers on systems with modern CPUs featuring deep instruction pipelining could use attacker controllable speculative execution over code patterns in the Linux Kernel to leak content from otherwise not readable memory in the same address space, allowing retrieval of passwords, cryptographic keys and other secrets.

  This problem is mitigated by adding speculative fencing on affected code paths throughout the Linux kernel.

• CVE-2017-5715: Local attackers on systems with modern CPUs featuring branch prediction could use mispredicted branches to speculatively execute code patterns that in turn could be made to leak other non-readable content in the same address space, an attack similar to CVE-2017-5753.

  This problem is mitigated by disabling predictive branches, depending on CPU architecture either by firmware updates and/or fixes in the user-kernel privilege boundaries.

  Please contact your CPU / hardware vendor for potential microcode or BIOS updates needed for this fix.

  As this feature can have a performance impact, it can be disabled using the 'nospec' kernel commandline option.

• CVE-2017-5754: Local attackers on systems with modern CPUs featuring deep instruction pipelining could use code patterns in userspace to speculative executive code that would read otherwise read protected memory, an attack similar to CVE-2017-5753.

  This problem is mitigated by unmapping the Linux Kernel from the user address space during user code execution, following a approach called 'KAISER'. The terms used here are 'KAISER' / 'Kernel Address Isolation' and 'PTI' / 'Page Table Isolation'.

  This feature is disabled on unaffected architectures.

  This feature can be enabled / disabled by the 'pti=[on|off|auto]' or 'nopti' commandline options.

The following security bugs were fixed:

• CVE-2017-1000251: The native Bluetooth stack in the Linux Kernel (BlueZ) was vulnerable to a stack overflow vulnerability in the processing of L2CAP configuration responses resulting in Remote code execution in kernel space (bnc#1057389).
• CVE-2017-11600: net/xfrm/xfrm_policy.c in the Linux kernel did not ensure that the dir value of xfrm_userpolicy_id is XFRM_POLICY_MAX or less, which allowed local users to cause a denial of service (out-of-bounds access) or possibly have unspecified other impact via an XFRM_MSG_MIGRATE xfrm Netlink message (bnc#1050231).
• CVE-2017-13080: Wi-Fi Protected Access (WPA and WPA2) allowed reinstallation of the Group Temporal Key (GTK) during the group key handshake, allowing an attacker within radio range to replay frames from access points to clients (bnc#1063667).
• CVE-2017-13167: An elevation of privilege vulnerability in the kernel sound timer was fixed. (bnc#1072876).
• CVE-2017-14106: The tcp_disconnect function in net/ipv4/tcp.c in the Linux kernel allowed local users to cause a denial of service (__tcp_select_window divide-by-zero error and system crash) by triggering a disconnect within a certain tcp_recvmsg code path (bnc#1056982).
• CVE-2017-14140: The move_pages system call in mm/migrate.c in the Linux kernel didn't check the effective uid of the target process, enabling a local attacker to learn the memory layout of a setuid executable despite ASLR (bnc#1057179).
• CVE-2017-14340: The XFS_IS_REALTIME_INODE macro in fs/xfs/xfs_linux.h in the Linux kernel did not verify that a filesystem has a realtime device, which allowed local users to cause a denial of service (NULL pointer dereference and OOPS) via vectors related to setting an RHINHERIT flag on a directory (bnc#1058524).
• CVE-2017-15102: The tower_probe function in drivers/usb/misc/legousbtower.c in the Linux kernel allowed local…

The SUSE Linux Enterprise 12 GA LTSS kernel was updated to receive various security and bugfixes.

This update adds mitigations for various side channel attacks against modern CPUs that could disclose content of otherwise unreadable memory (bnc#1068032).

• CVE-2017-5753 / 'SpectreAttack': Local attackers on systems with modern CPUs featuring deep instruction pipelining could use attacker controllable speculative execution over code patterns in the Linux Kernel to leak content from otherwise not readable memory in the same address space, allowing retrieval of passwords, cryptographic keys and other secrets.

  This problem is mitigated by adding speculative fencing on affected code paths throughout the Linux kernel.

  This issue is addressed for the x86_64, the IBM Power and IBM zSeries architecture.

• CVE-2017-5715 / 'SpectreAttack': Local attackers on systems with modern CPUs featuring branch prediction could use mispredicted branches to speculatively execute code patterns that in turn could be made to leak other non-readable content in the same address space, an attack similar to CVE-2017-5753.

  This problem is mitigated by disabling predictive branches, depending on CPU architecture either by firmware updates and/or fixes in the user-kernel privilege boundaries.

  This is done with help of Linux Kernel fixes on the Intel/AMD x86_64 and IBM zSeries architectures. On x86_64, this requires also updates of the CPU microcode packages, delivered in seperate updates.

  For IBM Power and zSeries the required firmware updates are supplied over regular channels by IBM.

  As this feature can have a performance impact, it can be disabled using the 'nospec' kernel commandline option.

• CVE-2017-5754 / 'MeltdownAttack': Local attackers on systems with modern CPUs featuring deep instruction pipelining could use code patterns in userspace to speculative executive code that would read otherwise read protected memory, an attack similar to CVE-2017-5753.

  This problem is mitigated by unmapping the Linux Kernel from the user address space during user code execution, following a approach called 'KAISER'. The terms used here are 'KAISER' / 'Kernel Address Isolation' and 'PTI' / 'Page Table Isolation'.

  This update does this on the x86_64 architecture, it is not required on the IBM zSeries architecture.

  This feature can be enabled / disabled by the 'pti=[on|off|auto]' or 'nopti' commandline options.

The following security bugs were fixed:

• CVE-2017-15868: The bnep_add_connection function in net/bluetooth/bnep/core.c in the Linux kernel did not ensure that an l2cap socket is available, which allowed local users to gain privileges via a crafted application (bnc#1071470).
• CVE-2017-13167: An elevation of privilege vulnerability in the kernel sound timer. (bnc#1072876).
• CVE-2017-16538: drivers/media/usb/dvb-usb-v2/lmedm04.c in the Linux kernel allowed local users to cause a denial of service (general protection fault and system crash) or possibly have unspecified other impact via a crafted USB device, related to a missing warm-start check and incorrect attach timing (dm04_lme2510_frontend_attach versus dm04_lme2510_tuner) (bnc#1066569).
• CVE-2017-17558: The usb_destroy_configuration function in drivers/usb/core/config.c in the USB core subsystem in the Linux kernel did not consider the maximum number of configurations and interfaces before attempting to release resources, which allowed local users to cause a denial of service (out-of-bounds write access) or possibly have unspecified other impact via a crafted USB device (bnc#1072561).
• CVE-2017-17450: net/netfilter/xt_osf.c in the Linux kernel did not require the CAP_NET_ADMIN capability for add_callback and remove_callback operations, which allowed local users to bypass intended access restrictions because the xt_osf_fingers data structure is shared across all net namespaces (bnc#1071695).
• CVE-2017-17449: The…

The SUSE Linux Enterprise 11 SP4 realtime kernel was updated to receive various security and bugfixes.

This update adds mitigations for various side channel attacks against modern CPUs that could disclose content of otherwise unreadable memory (bnc#1068032).

• CVE-2017-5753: Local attackers on systems with modern CPUs featuring deep instruction pipelining could use attacker controllable speculative execution over code patterns in the Linux Kernel to leak content from otherwise not readable memory in the same address space, allowing retrieval of passwords, cryptographic keys and other secrets.

  This problem is mitigated by adding speculative fencing on affected code paths throughout the Linux kernel.

• CVE-2017-5715: Local attackers on systems with modern CPUs featuring branch prediction could use mispredicted branches to speculatively execute code patterns that in turn could be made to leak other non-readable content in the same address space, an attack similar to CVE-2017-5753.

  This problem is mitigated by disabling predictive branches, depending on CPU architecture either by firmware updates and/or fixes in the user-kernel privilege boundaries.

  This is done with help of Linux Kernel fixes on the Intel/AMD x86_64 architectures. On x86_64, this requires also updates of the CPU microcode packages, delivered in seperate updates.

  As this feature can have a performance impact, it can be disabled using the 'nospec' kernel commandline option.

• CVE-2017-5754: Local attackers on systems with modern CPUs featuring deep instruction pipelining could use code patterns in userspace to speculative executive code that would read otherwise read protected memory, an attack similar to CVE-2017-5753.

  This problem is mitigated by unmapping the Linux Kernel from the user address space during user code execution, following a approach called 'KAISER'. The terms used here are 'KAISER' / 'Kernel Address Isolation' and 'PTI' / 'Page Table Isolation'.

The following security bugs were fixed:

• CVE-2017-11600: net/xfrm/xfrm_policy.c in the Linux kernel did not ensure that the dir value of xfrm_userpolicy_id is XFRM_POLICY_MAX or less, which allowed local users to cause a denial of service (out-of-bounds access) or possibly have unspecified other impact via an XFRM_MSG_MIGRATE xfrm Netlink message (bnc#1050231).
• CVE-2017-13167: An elevation of privilege vulnerability in the kernel sound timer was fixed. (bnc#1072876).
• CVE-2017-14106: The tcp_disconnect function in net/ipv4/tcp.c in the Linux kernel allowed local users to cause a denial of service (__tcp_select_window divide-by-zero error and system crash) by triggering a disconnect within a certain tcp_recvmsg code path (bnc#1056982).
• CVE-2017-15102: The tower_probe function in drivers/usb/misc/legousbtower.c in the Linux kernel allowed local users (who are physically proximate for inserting a crafted USB device) to gain privileges by leveraging a write-what-where condition that occurs after a race condition and a NULL pointer dereference (bnc#1066705).
• CVE-2017-15115: The sctp_do_peeloff function in net/sctp/socket.c in the Linux kernel did not check whether the intended netns is used in a peel-off action, which allowed local users to cause a denial of service (use-after-free and system crash) or possibly have unspecified other impact via crafted system calls (bnc#1068671).
• CVE-2017-15868: The bnep_add_connection function in net/bluetooth/bnep/core.c in the Linux kernel did not ensure that an l2cap socket is available, which allowed local users to gain privileges via a crafted application (bnc#1071470).
• CVE-2017-16525: The usb_serial_console_disconnect function in drivers/usb/serial/console.c in the Linux kernel allowed local users to cause a denial of service (use-after-free and system crash) or possibly have unspecified other impact via a crafted USB device, related to disconnection and failed setup (bnc#1066618). -…

The SUSE Linux Enterprise 12 SP2 Realtime kernel was updated to 4.4.104 to receive various security and bugfixes.

This update adds mitigations for various side channel attacks against modern CPUs that could disclose content of otherwise unreadable memory (bnc#1068032).

• CVE-2017-5753: Local attackers on systems with modern CPUs featuring deep instruction pipelining could use attacker controllable speculative execution over code patterns in the Linux Kernel to leak content from otherwise not readable memory in the same address space, allowing retrieval of passwords, cryptographic keys and other secrets.

  This problem is mitigated by adding speculative fencing on affected code paths throughout the Linux kernel.

• CVE-2017-5715: Local attackers on systems with modern CPUs featuring branch prediction could use mispredicted branches to speculatively execute code patterns that in turn could be made to leak other non-readable content in the same address space, an attack similar to CVE-2017-5753.

  This problem is mitigated by disabling predictive branches, depending on CPU architecture either by firmware updates and/or fixes in the user-kernel privilege boundaries.

  This is done with help of Linux Kernel fixes on the Intel/AMD x86_64 architectures. On x86_64, this requires also updates of the CPU microcode packages, delivered in seperate updates.

  As this feature can have a performance impact, it can be disabled using the 'nospec' kernel commandline option.

• CVE-2017-5754: Local attackers on systems with modern CPUs featuring deep instruction pipelining could use code patterns in userspace to speculative executive code that would read otherwise read protected memory, an attack similar to CVE-2017-5753.

  This problem is mitigated by unmapping the Linux Kernel from the user address space during user code execution, following a approach called 'KAISER'. The terms used here are 'KAISER' / 'Kernel Address Isolation' and 'PTI' / 'Page Table Isolation'.

The following security bugs were fixed:

• CVE-2017-1000405: The Linux Kernel versions had a problematic use of pmd_mkdirty() in the touch_pmd() function inside the THP implementation. touch_pmd() can be reached by get_user_pages(). In such case, the pmd will become dirty. This scenario breaks the new can_follow_write_pmd()'s logic - pmd can become dirty without going through a COW cycle. This bug is not as severe as the original 'Dirty cow' because an ext4 file (or any other regular file) cannot be mapped using THP. Nevertheless, it did allow us to overwrite read-only huge pages. For example, the zero huge page and sealed shmem files can be overwritten (since their mapping can be populated using THP). Note that after the first write page-fault to the zero page, it will be replaced with a new fresh (and zeroed) thp (bnc#1069496).
• CVE-2017-1000410: The Linux kernel was affected by a vulnerability that lies in the processing of incoming L2CAP commands - ConfigRequest, and ConfigResponse messages. (bnc#1070535).
• CVE-2017-11600: net/xfrm/xfrm_policy.c in the Linux kernel did not ensure that the dir value of xfrm_userpolicy_id is XFRM_POLICY_MAX or less, which allowed local users to cause a denial of service (out-of-bounds access) or possibly have unspecified other impact via an XFRM_MSG_MIGRATE xfrm Netlink message (bnc#1050231).
• CVE-2017-12193: The assoc_array_insert_into_terminal_node function in lib/assoc_array.c in the Linux kernel mishandled node splitting, which allowed local users to cause a denial of service (NULL pointer dereference and panic) via a crafted application, as demonstrated by the keyring key type, and key addition and link creation operations (bnc#1066192).
• CVE-2017-15115: The sctp_do_peeloff function in net/sctp/socket.c in the Linux kernel did not check whether the intended netns is used in a peel-off action, which allowed local users to cause a denial of service (use-after-free and system crash) or…

This update for webkit2gtk3 fixes the following issues:

Update to version 2.18.5:

• Disable SharedArrayBuffers from Web API.
• Reduce the precision of 'high' resolution time to 1ms.
• bsc#1075419 - Security fixes: includes improvements to mitigate the effects of Spectre and Meltdown (CVE-2017-5753 and CVE-2017-5715).

Update to version 2.18.4:

• Make WebDriver implementation more spec compliant.
• Fix a bug when trying to remove cookies before a web process is spawned.
• WebKitWebDriver process no longer links to libjavascriptcoregtk.
• Fix several memory leaks in GStreamer media backend.
• bsc#1073654 - Security fixes: CVE-2017-13866, CVE-2017-13870, CVE-2017-7156, CVE-2017-13856.

Update to version 2.18.3:

• Improve calculation of font metrics to prevent scrollbars from being shown unnecessarily in some cases.
• Fix handling of null capabilities in WebDriver implementation.
• Security fixes: CVE-2017-13798, CVE-2017-13788, CVE-2017-13803.

Update to version 2.18.2:

• Fix rendering of arabic text.
• Fix a crash in the web process when decoding GIF images.
• Fix rendering of wind in Windy.com.
• Fix several crashes and rendering issues.

Update to version 2.18.1:

• Improve performance of GIF animations.
• Fix garbled display in GMail.
• Fix rendering of several material design icons when using the web font.
• Fix flickering when resizing the window in Wayland.
• Prevent default kerberos authentication credentials from being used in ephemeral sessions.
• Fix a crash when webkit_web_resource_get_data() is cancelled.
• Correctly handle touchmove and touchend events in WebKitWebView.
• Fix the build with enchant 2.1.1.
• Fix the build in HPPA and Alpha.
• Fix several crashes and rendering issues.
• Security fixes: CVE-2017-7081, CVE-2017-7087, CVE-2017-7089, CVE-2017-7090, CVE-2017-7091, CVE-2017-7092, CVE-2017-7093, CVE-2017-7094, CVE-2017-7095, CVE-2017-7096, CVE-2017-7098, CVE-2017-7099, CVE-2017-7100, CVE-2017-7102, CVE-2017-7104, CVE-2017-7107, CVE-2017-7109, CVE-2017-7111, CVE-2017-7117, CVE-2017-7120, CVE-2017-7142.

• Enable gold linker on s390/s390x on SLE15/Tumbleweed.

This update fixes the following issues:

!!!NOTE: For PostgreSQL, schema migrations could take a long time (hours), depending on the number of synced !!! !!!packages and number of rows which requires cleanup. Please refer to the release notes for more information.!!!

nutch:

• Fix log hadoop into proper directory. (bsc#1061574)

osad:

• Fixed TypeError for force flag in setup_config that could happen when jabberd restart was needed. (bsc#1064393)

pxe-default-image:

• Spectre and Meltdown mitigation. (CVE-2017-5753, CVE-2017-5715, CVE-2017-5754, bsc#1068032)

spacecmd:

• Added custom JSON encoder in order to parse date fields correctly. (bsc#1070372)

spacewalk-backend:

• Fix restore hostname and ip*addr in templated documents. (bsc#1075044)
• Fix directory name in spacewalk-data-fsck.
• RhnServerNetwork refactoring. (bsc#1063419)

spacewalk-branding:

• Fix message about package profile synchronization. (bsc#1073739)
• Fix naming of the Tools channel. (bsc#979633)

spacewalk-client-tools:

• Fix package sources.

spacewalk-java:

• Fix message about package profile synchronization. (bsc#1073739)
• Add VM state as info gathered from VMware. (bsc#1063759)
• Improve performance of token checking, when RPMs or metadata are downloaded from minions. (bsc#1061273)
• Fix action names and date formatting in system event history. (bsc#1073713)
• Fix incorrect 'os-release' report after SP migration. (bsc#1071553)
• Fix failed package installation when in RES 32 and 64 bit packages are installed together. (bsc#1071314)
• Add user preferences in order to change items-per-page. (bsc#1055296)
• Display messages about wrong input more end-user friendly. (bsc#1015956)
• Fix content refresh when product keys change. (bsc#1069943)
• Allow 'Package List Refresh' when package architecture has changed. (bsc#1065259)
• Support Open Enterprise Server 2018. (bsc#1060182)
• Do not remove virtual instances for registered systems. (bsc#1063759)
• Process right configfile on 'scheduleFileComparisons' API calls. (bsc#1066663)
• Fix reported UUIDs for guests instances within a virtual host. (bsc#1063759)
• Generate Order Items for OEM subscriptions. (bsc#1045141)
• Enable 'Power Management' features on Salt minions.
• Fail gracefully when GPG files are requested. (bsc#1065676)
• Improve messaging for 'Compare Packages'. (bsc#1065844)
• RhnServerNetwork refactoring. (bsc#1063419)
• Add Adelaide timezone to selectable timezones. (bsc#1063891)

spacewalk-reports:

• More rhnServerNetwork refactoring. (bsc#1063419)

spacewalk-search:

• RhnServerNetwork refactoring. (bsc#1063419)

spacewalk-web:

• Add user preferences in order to change items-per-page. (bsc#1055296)

susemanager:

• Support Open Enterprise Server 2018. (bsc#1060182)
• Fixed bootstrap repository path for SLES4SAP version 12 and 12.1. (bsc#1062936)
• Fix error message for database upgrade failure.
• Check for sufficient diskspace in /var/lib/pgsql.
• Notify admin that database backups need reconfiguration after db upgrade.

susemanager-docs_en:

• Update text and image files:
  • List Open Enterprise Server 2015, 2015 SP1, 2018 as supported clients.

susemanager-schema:

• Fix hostname schema upgrade. (bsc#1076622)
• Fix duplicate entries in channel listings.
• Handle nevra not found case while fixing duplicate evr ids. (bsc#1074508)
• Enable 'Power Management' features on Salt minions.
• Fix unique index for evr and capability and remove duplicates during migration. (bsc#1058110)
• RhnServerNetwork refactoring. (bsc#1063419)
• Add Adelaide timezone to selectable timezones. (bsc#1063891)

susemanager-sls:

• Python3 compatibility fixes in modules and states.
• Fix failing certs state for Tumbleweed. (bsc#970630)
• Fix deprecated SLS files to avoid deprecation warnings during highstate. (bsc#1041993)

susemanager-sync-data:

• Support Open Enterprise Server 2018. (bsc#1060182)
• Fix description for HA channel. (bsc#1063588)
• Add support for CAASP. (bsc#1052283)
• Add IBM DLPAR channels…

This update for xen fixes several issues.

These security issues were fixed:

• CVE-2017-5753, CVE-2017-5715, CVE-2017-5754: Prevent information leaks via side effects of speculative execution, aka 'Spectre' and 'Meltdown' attacks (bsc#1074562, bsc#1068032)
• CVE-2017-15595: x86 PV guest OS users were able to cause a DoS (unbounded recursion, stack consumption, and hypervisor crash) or possibly gain privileges via crafted page-table stacking (bsc#1061081)
• CVE-2017-17566: Prevent PV guest OS users to cause a denial of service (host OS crash) or gain host OS privileges in shadow mode by mapping a certain auxiliary page (bsc#1070158).
• CVE-2017-17563: Prevent guest OS users to cause a denial of service (host OS crash) or gain host OS privileges by leveraging an incorrect mask for reference-count overflow checking in shadow mode (bsc#1070159).
• CVE-2017-17564: Prevent guest OS users to cause a denial of service (host OS crash) or gain host OS privileges by leveraging incorrect error handling for reference counting in shadow mode (bsc#1070160).
• CVE-2017-17565: Prevent PV guest OS users to cause a denial of service (host OS crash) if shadow mode and log-dirty mode are in place, because of an incorrect assertion related to M2P (bsc#1070163).
• CVE-2018-5683: The vga_draw_text function allowed local OS guest privileged users to cause a denial of service (out-of-bounds read and QEMU process crash) by leveraging improper memory address validation (bsc#1076116).
• CVE-2017-18030: The cirrus_invalidate_region function allowed local OS guest privileged users to cause a denial of service (out-of-bounds array access and QEMU process crash) via vectors related to negative pitch (bsc#1076180).

These non-security issues were fixed:

• bsc#1067317: pass cache=writeback|unsafe|directsync to qemu depending on the libxl disk settings
• bsc#1051729: Prevent invalid symlinks after install of SLES 12 SP2
• bsc#1035442: Increased the value of LIBXL_DESTROY_TIMEOUT from 10 to 100 seconds. If many domUs shutdown in parallel the backends couldn't keep up
• bsc#1027519: Added several upstream patches

This update for xen fixes several issues.

These security issues were fixed:

• CVE-2017-5753, CVE-2017-5715, CVE-2017-5754: Prevent information leaks via side effects of speculative execution, aka 'Spectre' and 'Meltdown' attacks (bsc#1074562, bsc#1068032)
• CVE-2017-15595: x86 PV guest OS users were able to cause a DoS (unbounded recursion, stack consumption, and hypervisor crash) or possibly gain privileges via crafted page-table stacking (bsc#1061081)
• CVE-2017-17566: Prevent PV guest OS users to cause a denial of service (host OS crash) or gain host OS privileges in shadow mode by mapping a certain auxiliary page (bsc#1070158).
• CVE-2017-17563: Prevent guest OS users to cause a denial of service (host OS crash) or gain host OS privileges by leveraging an incorrect mask for reference-count overflow checking in shadow mode (bsc#1070159).
• CVE-2017-17564: Prevent guest OS users to cause a denial of service (host OS crash) or gain host OS privileges by leveraging incorrect error handling for reference counting in shadow mode (bsc#1070160).
• CVE-2017-17565: Prevent PV guest OS users to cause a denial of service (host OS crash) if shadow mode and log-dirty mode are in place, because of an incorrect assertion related to M2P (bsc#1070163).
• CVE-2018-5683: The vga_draw_text function allowed local OS guest privileged users to cause a denial of service (out-of-bounds read and QEMU process crash) by leveraging improper memory address validation (bsc#1076116).
• CVE-2017-18030: The cirrus_invalidate_region function allowed local OS guest privileged users to cause a denial of service (out-of-bounds array access and QEMU process crash) via vectors related to negative pitch (bsc#1076180).

These non-security issues were fixed:

• bsc#1051729: Prevent invalid symlinks after install of SLES 12 SP2
• bsc#1035442: Increased the value of LIBXL_DESTROY_TIMEOUT from 10 to 100 seconds. If many domUs shutdown in parallel the backends couldn't keep up
• bsc#1027519: Added several upstream patches

This update fixes the following issues:

nutch:

• Fix hadoop log dir. (bsc#1061574)

osad, rhnlib:

• Fix update mechanism when updating the updateservice (bsc#1073619)

pxe-default-image:

• Spectre and Meltdown mitigation. (CVE-2017-5753, CVE-2017-5715, CVE-2017-5754, bsc#1068032)

spacecmd:

• Support multiple FQDNs per system. (bsc#1063419)
• Added custom JSON encoder in order to parse date fields correctly. (bsc#1070372)

spacewalk-backend:

• Fix spacewalk-data-fsck restore of broken package database entry. (bsc#1071526)
• Support multiple FQDNs per system. (bsc#1063419)
• Fix restore hostname and ip*addr in templated documents. (bsc#1075044)
• Fix directory name in spacewalk-data-fsck.

spacewalk-branding:

• Replace custom states with configuration channels.
• Fix pre formatted code. (bsc#1067608)
• Fix message about package profile sync. (bsc#1073739)
• Fix naming of the Tools channel. (bsc#979633)

spacewalk-client-tools:

• Support multiple FQDNs per system. (bsc#1063419)
• Fix update mechanism when updating the updateservice. (bsc#1073619)

spacewalk-java:

• Fix the file count for deployed files. (bsc#1074300)
• Remove previous activation keys when migrating to salt. (bsc#1031081)
• Improve webui for comparing files. (bsc#1076201)
• Separate Salt calls based on config revisions and server grouping. (bsc#1074854)
• For minion, no option to modifiy config file but just view.
• Handle gpg_check correctly. (bsc#1076578)
• Uniform date formatting in System Details view. (bsc#1045289)
• Import content of custom states from filesystem to database on startup, backup old state files.
• Change the directory of the (normal) configuration channels from mgr_cfg_org_N to manager_org_N.
• Replace custom states with configuration channels.
• Hide ownership/permission fields from create/upload config file forms for state channels. (bsc#1072153)
• Hide files from state channels from deploy/compare file lists. (bsc#1072160)
• Disable and hide deploy files tab for state config channels. (bsc#1072157)
• Allow ordering config channels in state revision.
• Disallow creating 'normal' config channels when a 'state' channel with the same name and org already exists and vice versa.
• UI has been updated to manage state channels.
• Support multiple FQDNs per system. (bsc#1063419)
• Setting 'Base Channels' as default tab for 'Channels' tab in SSM Overview screen. (bsc#979616)
• Log triggers that are in ERROR state.
• Refresh pillar data on formular change. (bsc#1028285)
• Uniform the notification message when rebooting a system. (bsc#1036302)
• Avoid use of the potentially-slow rhnServerNeededPackageCache view.
• Speed up scheduling of package updates through the SSM. (bsc#1076034)
• Fix encoding/decoding of url_bounce with more parameters. (bsc#1075408)
• After dry-run, sync channels back with the server. (bsc#1071468)
• Fix message about package profile sync. (bsc#1073739)
• On registration, assign server to the organization of the creator when activation key is empty. (bsc#1016377)
• Fix logging issues when saving autoyast profiles. (bsc#1073474)
• Add VM state as info gathered from VMware. (bsc#1063759)
• Improve performance of token checking, when RPMs or metadata are downloaded from minions. (bsc#1061273)
• Allow selecting unnamed context in kubeconfig. (bsc#1073482)
• Fix action names and date formatting in system event history. (bsc#1073713)
• Fix incorrect 'os-release' report after SP migration. (bsc#1071553)
• Fix failed package installation when in RES 32 and 64 bit packages are installed together. (bsc#1071314)
• Add user preferences in order to change items-per-page. (bsc#1055296)
• Order salt formulas alphabetically. (bsc#1022077)
• Improved error message. (bsc#1064258)
• Display messages about wrong input more end-user friendly. (bsc#1015956)
• Add api calls for content staging.
• Fix content refresh when product keys change. (bsc#1069943)
• Allow 'Package List Refresh' when package arch has changed. (bsc#1065259)
• New API…

This update fixes the following issues:

nutch:

• Fix hadoop log dir. (bsc#1061574)

osad, rhnlib:

• Fix update mechanism when updating the updateservice (bsc#1073619)

pxe-default-image:

• Spectre and Meltdown mitigation. (CVE-2017-5753, CVE-2017-5715, CVE-2017-5754, bsc#1068032)

spacecmd:

• Support multiple FQDNs per system. (bsc#1063419)
• Added custom JSON encoder in order to parse date fields correctly. (bsc#1070372)

spacewalk-backend:

• Fix spacewalk-data-fsck restore of broken package database entry. (bsc#1071526)
• Support multiple FQDNs per system. (bsc#1063419)
• Fix restore hostname and ip*addr in templated documents. (bsc#1075044)
• Fix directory name in spacewalk-data-fsck.

spacewalk-branding:

• Replace custom states with configuration channels.
• Fix pre formatted code. (bsc#1067608)
• Fix message about package profile sync. (bsc#1073739)
• Fix naming of the Tools channel. (bsc#979633)

spacewalk-client-tools:

• Support multiple FQDNs per system. (bsc#1063419)
• Fix update mechanism when updating the updateservice. (bsc#1073619)

spacewalk-java:

• Fix the file count for deployed files. (bsc#1074300)
• Remove previous activation keys when migrating to salt. (bsc#1031081)
• Improve webui for comparing files. (bsc#1076201)
• Separate Salt calls based on config revisions and server grouping. (bsc#1074854)
• For minion, no option to modifiy config file but just view.
• Handle gpg_check correctly. (bsc#1076578)
• Uniform date formatting in System Details view. (bsc#1045289)
• Import content of custom states from filesystem to database on startup, backup old state files.
• Change the directory of the (normal) configuration channels from mgr_cfg_org_N to manager_org_N.
• Replace custom states with configuration channels.
• Hide ownership/permission fields from create/upload config file forms for state channels. (bsc#1072153)
• Hide files from state channels from deploy/compare file lists. (bsc#1072160)
• Disable and hide deploy files tab for state config channels. (bsc#1072157)
• Allow ordering config channels in state revision.
• Disallow creating 'normal' config channels when a 'state' channel with the same name and org already exists and vice versa.
• UI has been updated to manage state channels.
• Support multiple FQDNs per system. (bsc#1063419)
• Setting 'Base Channels' as default tab for 'Channels' tab in SSM Overview screen. (bsc#979616)
• Log triggers that are in ERROR state.
• Refresh pillar data on formular change. (bsc#1028285)
• Uniform the notification message when rebooting a system. (bsc#1036302)
• Avoid use of the potentially-slow rhnServerNeededPackageCache view.
• Speed up scheduling of package updates through the SSM. (bsc#1076034)
• Fix encoding/decoding of url_bounce with more parameters. (bsc#1075408)
• After dry-run, sync channels back with the server. (bsc#1071468)
• Fix message about package profile sync. (bsc#1073739)
• On registration, assign server to the organization of the creator when activation key is empty. (bsc#1016377)
• Fix logging issues when saving autoyast profiles. (bsc#1073474)
• Add VM state as info gathered from VMware. (bsc#1063759)
• Improve performance of token checking, when RPMs or metadata are downloaded from minions. (bsc#1061273)
• Allow selecting unnamed context in kubeconfig. (bsc#1073482)
• Fix action names and date formatting in system event history. (bsc#1073713)
• Fix incorrect 'os-release' report after SP migration. (bsc#1071553)
• Fix failed package installation when in RES 32 and 64 bit packages are installed together. (bsc#1071314)
• Add user preferences in order to change items-per-page. (bsc#1055296)
• Order salt formulas alphabetically. (bsc#1022077)
• Improved error message. (bsc#1064258)
• Display messages about wrong input more end-user friendly. (bsc#1015956)
• Add api calls for content staging.
• Fix content refresh when product keys change. (bsc#1069943)
• Allow 'Package List Refresh' when package arch has changed. (bsc#1065259)
• New API…