Skip to content
OpenAdvisories
Medium SUSE-SU-2018:0011-1 17 CVEs

Security update for the Linux Kernel

Published Jan 4, 2018 · Updated Feb 4, 2026

Summary

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 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-8824: The dccp_disconnect function in net/dccp/proto.c in the Linux kernel allowed local users to gain privileges or cause a denial of service (use-after-free) via an AF_UNSPEC connect system call during the DCCP_LISTEN state (bnc#1070771).
- CVE-2017-16939: The XFRM dump policy implementation in net/xfrm/xfrm_user.c in the Linux kernel allowed local users to gain privileges or cause a denial of service (use-after-free) via a crafted SO_RCVBUF setsockopt system call in conjunction with XFRM_MSG_GETPOLICY Netlink messages (bnc#1069702).
- 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-14106: The tcp_disconnect function in net/ipv4/tcp.c in the Linux kernel allowed local users to cause a de

Fixed packages 19

ReleasePackageFixed in
SUSE · SLES 11 SP4 Linux Enterprise Server 11 SP4 kernel-bigmem 3.0.101-108.21.1
SUSE · SLES 11 SP4 Linux Enterprise Server 11 SP4 kernel-default 3.0.101-108.21.1
SUSE · SLES 11 SP4 Linux Enterprise Server 11 SP4 kernel-ec2 3.0.101-108.21.1
SUSE · SLES 11 SP4 Linux Enterprise Server 11 SP4 kernel-pae 3.0.101-108.21.1
SUSE · SLES 11 SP4 Linux Enterprise Server 11 SP4 kernel-ppc64 3.0.101-108.21.1
SUSE · SLES 11 SP4 Linux Enterprise Server 11 SP4 kernel-source 3.0.101-108.21.1
SUSE · SLES 11 SP4 Linux Enterprise Server 11 SP4 kernel-syms 3.0.101-108.21.1
SUSE · SLES 11 SP4 Linux Enterprise Server 11 SP4 kernel-trace 3.0.101-108.21.1
SUSE · SLES 11 SP4 Linux Enterprise Server 11 SP4 kernel-xen 3.0.101-108.21.1
SUSE · SLES for SAP 11 SP4 Linux Enterprise Server for SAP Applications 11 SP4 kernel-bigmem 3.0.101-108.21.1
SUSE · SLES for SAP 11 SP4 Linux Enterprise Server for SAP Applications 11 SP4 kernel-default 3.0.101-108.21.1
SUSE · SLES for SAP 11 SP4 Linux Enterprise Server for SAP Applications 11 SP4 kernel-ec2 3.0.101-108.21.1
SUSE · SLES for SAP 11 SP4 Linux Enterprise Server for SAP Applications 11 SP4 kernel-pae 3.0.101-108.21.1
SUSE · SLES for SAP 11 SP4 Linux Enterprise Server for SAP Applications 11 SP4 kernel-ppc64 3.0.101-108.21.1
SUSE · SLES for SAP 11 SP4 Linux Enterprise Server for SAP Applications 11 SP4 kernel-source 3.0.101-108.21.1
SUSE · SLES for SAP 11 SP4 Linux Enterprise Server for SAP Applications 11 SP4 kernel-syms 3.0.101-108.21.1
SUSE · SLES for SAP 11 SP4 Linux Enterprise Server for SAP Applications 11 SP4 kernel-trace 3.0.101-108.21.1
SUSE · SLES for SAP 11 SP4 Linux Enterprise Server for SAP Applications 11 SP4 kernel-xen 3.0.101-108.21.1
SUSE · SLES 11 SP4 Linux Enterprise Software Development Kit 11 SP4 kernel-docs 3.0.101-108.21.2

Vulnerabilities 17

References

  • report
    https://bugzilla.suse.com/1013018
  • report
    https://bugzilla.suse.com/1024612
  • report
    https://bugzilla.suse.com/1034862
  • report
    https://bugzilla.suse.com/1045479
  • report
    https://bugzilla.suse.com/1045538
  • report
    https://bugzilla.suse.com/1047487
  • report
    https://bugzilla.suse.com/1048185
  • report
    https://bugzilla.suse.com/1050231
  • report
    https://bugzilla.suse.com/1050431
  • report
    https://bugzilla.suse.com/1056982
  • report
    https://bugzilla.suse.com/1063043
  • report
    https://bugzilla.suse.com/1065180
  • report
    https://bugzilla.suse.com/1065600
  • report
    https://bugzilla.suse.com/1066569
  • report
    https://bugzilla.suse.com/1066693
  • report
    https://bugzilla.suse.com/1066973
  • report
    https://bugzilla.suse.com/1068032
  • report
    https://bugzilla.suse.com/1068671
  • report
    https://bugzilla.suse.com/1068984
  • report
    https://bugzilla.suse.com/1069702
  • report
    https://bugzilla.suse.com/1070771
  • report
    https://bugzilla.suse.com/1070964
  • report
    https://bugzilla.suse.com/1071074
  • report
    https://bugzilla.suse.com/1071470
  • report
    https://bugzilla.suse.com/1071695
  • report
    https://bugzilla.suse.com/1072457
  • report
    https://bugzilla.suse.com/1072561
  • report
    https://bugzilla.suse.com/1072876
  • report
    https://bugzilla.suse.com/1073792
  • report
    https://bugzilla.suse.com/1073874
  • web
    https://www.suse.com/security/cve/CVE-2017-11600
  • web
    https://www.suse.com/security/cve/CVE-2017-13167
  • web
    https://www.suse.com/security/cve/CVE-2017-14106
  • web
    https://www.suse.com/security/cve/CVE-2017-15115
  • web
    https://www.suse.com/security/cve/CVE-2017-15868
  • web
    https://www.suse.com/security/cve/CVE-2017-16534
  • web
    https://www.suse.com/security/cve/CVE-2017-16538
  • web
    https://www.suse.com/security/cve/CVE-2017-16939
  • web
    https://www.suse.com/security/cve/CVE-2017-17450