Synopsis
The remote SUSE host is missing one or more security updates.
Description
The SUSE Linux Enterprise 12 SP2 LTSS kernel was updated to receive
various security and bugfixes.
CVE-2018-10853: A flaw was found in the way the KVM hypervisor
emulated instructions such as sgdt/sidt/fxsave/fxrstor. It did not
check current privilege(CPL) level while emulating unprivileged
instructions. An unprivileged guest user/process could use this flaw
to potentially escalate privileges inside guest (bnc#1097104).
CVE-2018-10876: A flaw was found in Linux kernel in the ext4
filesystem code. A use-after-free is possible in
ext4_ext_remove_space() function when mounting and operating a crafted
ext4 image. (bnc#1099811)
CVE-2018-10877: Linux kernel ext4 filesystem is vulnerable to an
out-of-bound access in the ext4_ext_drop_refs() function when
operating on a crafted ext4 filesystem image. (bnc#1099846)
CVE-2018-10878: A flaw was found in the Linux kernel's ext4
filesystem. A local user can cause an out-of-bounds write and a denial
of service or unspecified other impact is possible by mounting and
operating a crafted ext4 filesystem image. (bnc#1099813)
CVE-2018-10879: A flaw was found in the Linux kernel's ext4
filesystem. A local user can cause a use-after-free in
ext4_xattr_set_entry function and a denial of service or unspecified
other impact may occur by renaming a file in a crafted ext4 filesystem
image. (bnc#1099844)
CVE-2018-10880: Linux kernel is vulnerable to a stack-out-of-bounds
write in the ext4 filesystem code when mounting and writing to a
crafted ext4 image in ext4_update_inline_data(). An attacker could use
this to cause a system crash and a denial of service. (bnc#1099845)
CVE-2018-10881: A flaw was found in the Linux kernel's ext4
filesystem. A local user can cause an out-of-bound access in
ext4_get_group_info function, a denial of service, and a system crash
by mounting and operating on a crafted ext4 filesystem image.
(bnc#1099864)
CVE-2018-10882: A flaw was found in the Linux kernel's ext4
filesystem. A local user can cause an out-of-bound write in in
fs/jbd2/transaction.c code, a denial of service, and a system crash by
unmounting a crafted ext4 filesystem image. (bnc#1099849)
CVE-2018-10883: A flaw was found in the Linux kernel's ext4
filesystem. A local user can cause an out-of-bounds write in
jbd2_journal_dirty_metadata(), a denial of service, and a system crash
by mounting and operating on a crafted ext4 filesystem image.
(bnc#1099863)
CVE-2018-10902: It was found that the raw midi kernel driver did not
protect against concurrent access which leads to a double realloc
(double free) in snd_rawmidi_input_params() and
snd_rawmidi_output_status() which are part of snd_rawmidi_ioctl()
handler in rawmidi.c file. A malicious local attacker could possibly
use this for privilege escalation (bnc#1105322).
CVE-2018-10938: A crafted network packet sent remotely by an attacker
may force the kernel to enter an infinite loop in the
cipso_v4_optptr() function in net/ipv4/cipso_ipv4.c leading to a
denial-of-service. A certain non-default configuration of LSM (Linux
Security Module) and NetLabel should be set up on a system before an
attacker could leverage this flaw (bnc#1106016).
CVE-2018-10940: The cdrom_ioctl_media_changed function in
drivers/cdrom/cdrom.c allowed local attackers to use a incorrect
bounds check in the CDROM driver CDROM_MEDIA_CHANGED ioctl to read out
kernel memory (bnc#1092903).
CVE-2018-12896: An Integer Overflow in kernel/time/posix-timers.c in
the POSIX timer code is caused by the way the overrun accounting
works. Depending on interval and expiry time values, the overrun can
be larger than INT_MAX, but the accounting is int based. This
basically made the accounting values, which are visible to user space
via timer_getoverrun(2) and siginfo::si_overrun, random. For example,
a local user can cause a denial of service (signed integer overflow)
via crafted mmap, futex, timer_create, and timer_settime system calls
(bnc#1099922).
CVE-2018-13093: There is a NULL pointer dereference and panic in
lookup_slow() on a NULL inode->i_ops pointer when doing pathwalks on a
corrupted xfs image. This occurs because of a lack of proper
validation that cached inodes are free during allocation
(bnc#1100001).
CVE-2018-13094: An OOPS may occur for a corrupted xfs image after
xfs_da_shrink_inode() is called with a NULL bp (bnc#1100000).
CVE-2018-13095: A denial of service (memory corruption and BUG) can
occur for a corrupted xfs image upon encountering an inode that is in
extent format, but has more extents than fit in the inode fork
(bnc#1099999).
CVE-2018-14617: There is a NULL pointer dereference and panic in
hfsplus_lookup() in fs/hfsplus/dir.c when opening a file (that is
purportedly a hard link) in an hfs+ filesystem that has malformed
catalog data, and is mounted read-only without a metadata directory
(bnc#1102870).
CVE-2018-14678: The xen_failsafe_callback entry point in
arch/x86/entry/entry_64.S did not properly maintain RBX, which allowed
local users to cause a denial of service (uninitialized memory usage
and system crash). Within Xen, 64-bit x86 PV Linux guest OS users can
trigger a guest OS crash or possibly gain privileges (bnc#1102715).
CVE-2018-15572: The spectre_v2_select_mitigation function in
arch/x86/kernel/cpu/bugs.c did not always fill RSB upon a context
switch, which made it easier for attackers to conduct
userspace-userspace spectreRSB attacks (bnc#1102517 bnc#1105296).
CVE-2018-15594: arch/x86/kernel/paravirt.c mishandled certain indirect
calls, which made it easier for attackers to conduct Spectre-v2
attacks against paravirtual guests (bnc#1105348).
CVE-2018-16276: Local attackers could use user access read/writes with
incorrect bounds checking in the yurex USB driver to crash the kernel
or potentially escalate privileges (bnc#1106095).
CVE-2018-16658: An information leak in cdrom_ioctl_drive_status in
drivers/cdrom/cdrom.c could be used by local attackers to read kernel
memory because a cast from unsigned long to int interferes with bounds
checking. This is similar to CVE-2018-10940 (bnc#1107689).
CVE-2018-17182: The vmacache_flush_all function in mm/vmacache.c
mishandled sequence number overflows. An attacker can trigger a
use-after-free (and possibly gain privileges) via certain thread
creation, map, unmap, invalidation, and dereference operations
(bnc#1108399).
CVE-2018-6554: Memory leak in the irda_bind function in
net/irda/af_irda.c and later in drivers/staging/irda/net/af_irda.c
allowed local users to cause a denial of service (memory consumption)
by repeatedly binding an AF_IRDA socket (bnc#1106509).
CVE-2018-6555: The irda_setsockopt function in net/irda/af_irda.c and
later in drivers/staging/irda/net/af_irda.c allowed local users to
cause a denial of service (ias_object use-after-free and system crash)
or possibly have unspecified other impact via an AF_IRDA socket
(bnc#1106511).
CVE-2018-7757: Memory leak in the sas_smp_get_phy_events function in
drivers/scsi/libsas/sas_expander.c allowed local users to cause a
denial of service (memory consumption) via many read accesses to files
in the /sys/class/sas_phy directory, as demonstrated by the
/sys/class/sas_phy/phy-1:0:12/invalid_dword_count file (bnc#1084536).
CVE-2018-9363: A buffer overflow in bluetooth HID report processing
could be used by malicious bluetooth devices to crash the kernel or
potentially execute code (bnc#1105292). The following security bugs
were fixed :
CVE-2018-7480: The blkcg_init_queue function in block/blk-cgroup.c
allowed local users to cause a denial of service (double free) or
possibly have unspecified other impact by triggering a creation
failure (bnc#1082863).
The update package also includes non-security fixes. See advisory for
details.
Note that Tenable Network Security has extracted the preceding
description block directly from the SUSE security advisory. Tenable
has attempted to automatically clean and format it as much as possible
without introducing additional issues.
Solution
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 OpenStack Cloud 7:zypper in -t patch
SUSE-OpenStack-Cloud-7-2018-2188=1
SUSE Linux Enterprise Server for SAP 12-SP2:zypper in -t patch
SUSE-SLE-SAP-12-SP2-2018-2188=1
SUSE Linux Enterprise Server 12-SP2-LTSS:zypper in -t patch
SUSE-SLE-SERVER-12-SP2-2018-2188=1
SUSE Linux Enterprise High Availability 12-SP2:zypper in -t patch
SUSE-SLE-HA-12-SP2-2018-2188=1
SUSE Enterprise Storage 4:zypper in -t patch
SUSE-Storage-4-2018-2188=1
OpenStack Cloud Magnum Orchestration 7:zypper in -t patch
SUSE-OpenStack-Cloud-Magnum-Orchestration-7-2018-2188=1