SUSE: 2019:1692-1 important: the Linux Kernel

    Date24 Jun 2019
    Posted ByLinuxSecurity Advisories
    An update that solves 9 vulnerabilities and has 7 fixes is now available.
       SUSE Security Update: Security update for the Linux Kernel
    Announcement ID:    SUSE-SU-2019:1692-1
    Rating:             important
    References:         #1090078 #1110785 #1113769 #1120843 #1120885 
                        #1125580 #1125931 #1131543 #1131587 #1132374 
                        #1132472 #1134848 #1135281 #1136424 #1136446 
    Cross-References:   CVE-2018-17972 CVE-2019-11190 CVE-2019-11477
                        CVE-2019-11478 CVE-2019-11479 CVE-2019-11833
                        CVE-2019-11884 CVE-2019-3846 CVE-2019-5489
    Affected Products:
                        SUSE Linux Enterprise Server 12-LTSS
                        SUSE Linux Enterprise Module for Public Cloud 12
       An update that solves 9 vulnerabilities and has 7 fixes is
       now available.
       The SUSE Linux Enterprise 12 kernel version 3.12.61 was updated to receive
       various security and bugfixes.
       The following security bugs were fixed:
       - CVE-2019-11477: A sequence of SACKs may have been crafted by a remote
         attacker such that one can trigger an integer overflow, leading to a
         kernel panic. (bsc#1137586).
       - CVE-2019-11478: It was possible to send a crafted sequence of SACKs
         which would fragment the TCP retransmission queue. A remote attacker may
         have been able to further exploit the fragmented queue to cause an
         expensive linked-list walk for subsequent SACKs received for that same
         TCP connection.
       - CVE-2019-11479: It was possible to send a crafted sequence of SACKs
         which would fragment the RACK send map. A remote attacker may have been
         able to further exploit the fragmented send map to cause an expensive
         linked-list walk for subsequent SACKs received for that same TCP
         connection. This would have resulted in excess resource consumption due
         to low mss values.
       - CVE-2019-3846: A flaw that allowed an attacker to corrupt memory and
         possibly escalate privileges was found in the mwifiex kernel module
         while connecting to a malicious wireless network. (bnc#1136424)
       - CVE-2019-5489: The mincore() implementation in mm/mincore.c in the Linux
         kernel allowed local attackers to observe page cache access patterns of
         other processes on the same system, potentially allowing sniffing of
         secret information. (Fixing this affects the output of the fincore
         program.) Limited remote exploitation may have been possible, as
         demonstrated by latency differences in accessing public files from an
         Apache HTTP Server. (bnc#1120843)
       - CVE-2019-11833: fs/ext4/extents.c in the Linux kernel did not zero out
         the unused memory region in the extent tree block, which might have
         allowed local users to obtain sensitive information by reading
         uninitialized data in the filesystem. (bnc#1135281)
       - CVE-2019-11190: The Linux kernel allowed local users to bypass ASLR on
         setuid programs (such as /bin/su) because install_exec_creds() is called
         too late in load_elf_binary() in fs/binfmt_elf.c, and thus the
         ptrace_may_access() check has a race condition when reading
         /proc/pid/stat. (bnc#1131543)
       - CVE-2019-11884: The do_hidp_sock_ioctl function in
         net/bluetooth/hidp/sock.c in the Linux kernel allowed a local user to
         obtain potentially sensitive information from kernel stack memory via a
         HIDPCONNADD command, because a name field may not end with a '\0'
         character. (bnc#1134848)
       - CVE-2018-17972: An issue was discovered in the proc_pid_stack function
         in fs/proc/base.c in the Linux kernel It did not ensure that only root
         may inspect the kernel stack of an arbitrary task, allowing a local
         attacker to exploit racy stack unwinding and leak kernel task stack
         contents. (bnc#1110785)
       The following non-security bugs were fixed:
       - kabi: drop LINUX_MIB_TCPWQUEUETOOBIG snmp counter (bsc#1137586).
       - lib: add "on"/"off" support to strtobool (bsc#1125931).
       - powerpc/tm: Add commandline option to disable hardware transactional
         memory (bsc#1125580).
       - powerpc/tm: Add TM Unavailable Exception (bsc#1125580).
       - powerpc/tm: Flip the HTM switch default to disabled (bsc#1125580).
       - powerpc/vdso32: fix CLOCK_MONOTONIC on PPC64 (bsc#1131587).
       - powerpc/vdso64: Fix CLOCK_MONOTONIC inconsistencies across Y2038
       - tcp: add tcp_min_snd_mss sysctl (bsc#1137586).
       - tcp: enforce tcp_min_snd_mss in tcp_mtu_probing() (bsc#1137586).
       - tcp: limit payload size of sacked skbs (bsc#1137586).
       - tcp: tcp_fragment() should apply sane memory limits (bsc#1137586).
    Special Instructions and Notes:
       Please reboot the system after installing this update.
    Patch Instructions:
       To install this SUSE Security Update use the SUSE recommended installation methods
       like YaST online_update or "zypper patch".
       Alternatively you can run the command listed for your product:
       - SUSE Linux Enterprise Server 12-LTSS:
          zypper in -t patch SUSE-SLE-SERVER-12-2019-1692=1
       - SUSE Linux Enterprise Module for Public Cloud 12:
          zypper in -t patch SUSE-SLE-Module-Public-Cloud-12-2019-1692=1
    Package List:
       - SUSE Linux Enterprise Server 12-LTSS (ppc64le s390x x86_64):
       - SUSE Linux Enterprise Server 12-LTSS (noarch):
       - SUSE Linux Enterprise Server 12-LTSS (x86_64):
       - SUSE Linux Enterprise Server 12-LTSS (s390x):
       - SUSE Linux Enterprise Module for Public Cloud 12 (x86_64):
    sle-security-updates mailing list
    This email address is being protected from spambots. You need JavaScript enabled to view it.
    You are not authorised to post comments.

    Comments powered by CComment

    LinuxSecurity Poll

    Do you read our distribution advisories on a regular basis?

    No answer selected. Please try again.
    Please select either existing option or enter your own, however not both.
    Please select minimum 0 answer(s) and maximum 3 answer(s).
    [{"id":"84","title":"Yes, for a single distribution","votes":"0","type":"x","order":"1","pct":0,"resources":[]},{"id":"85","title":"Yes, for multiple distributions","votes":"5","type":"x","order":"2","pct":62.5,"resources":[]},{"id":"86","title":"No","votes":"3","type":"x","order":"3","pct":37.5,"resources":[]}]["#ff5b00","#4ac0f2","#b80028","#eef66c","#60bb22","#b96a9a","#62c2cc"]["rgba(255,91,0,0.7)","rgba(74,192,242,0.7)","rgba(184,0,40,0.7)","rgba(238,246,108,0.7)","rgba(96,187,34,0.7)","rgba(185,106,154,0.7)","rgba(98,194,204,0.7)"]350

    We use cookies to provide and improve our services. By using our site, you consent to our Cookie Policy.