File _patchinfo of Package patchinfo.8315

<patchinfo incident="8315">
  <issue id="1097108" tracker="bnc">VUL-0: CVE-2018-10853: kernel live patch: kvm: guest userspace to guest kernel write</issue>
  <issue id="1099306" tracker="bnc">VUL-0: EMBARGOED: CVE-2018-3646: kernel live patch: kvm: L1 Terminal Fault - OS</issue>
  <issue id="1102682" tracker="bnc">VUL-0: CVE-2018-5390: kernel live patch: denial of service conditions with low rates of specially modified packets aka "SegmentSmack"</issue>
  <issue id="1103203" tracker="bnc">VUL-0: CVE-2017-18344: kernel live patch: The timer_create syscall implementationdoesn't properly validate the sigevent-&gt;sigev_notifyfield, which leads to out-of-bounds access</issue>
  <issue id="2017-18344" tracker="cve" />
  <issue id="2018-10853" tracker="cve" />
  <issue id="2018-3646" tracker="cve" />
  <issue id="2018-5390" tracker="cve" />
  <description>This update for the Linux Kernel 4.12.14-25_3 fixes several issues.

The following security issues were fixed:

- CVE-2018-5390: Linux kernel versions 4.9+ can be forced to make very expensive calls to tcp_collapse_ofo_queue() and tcp_prune_ofo_queue() for every incoming packet which can lead to a denial of service (bsc#1102682).
- CVE-2018-3646: Local attackers in virtualized guest systems could use speculative code patterns on hyperthreaded processors to read data present in the L1 Datacache used by other hyperthreads on the same CPU core, potentially leaking sensitive data, even from other virtual machines or the host system (bsc#1099306).
- CVE-2017-18344: The timer_create syscall implementation in kernel/time/posix-timers.c didn't properly validate the sigevent-&gt;sigev_notify field, which lead to out-of-bounds access in the show_timer function (called when /proc/$PID/timers is read). This allowed userspace applications to read arbitrary kernel memory (on a kernel built with CONFIG_POSIX_TIMERS and CONFIG_CHECKPOINT_RESTORE) (bsc#1103203).
before 4.14.8
- CVE-2018-10853: A flaw was found in kvm. In which certain instructions such as sgdt/sidt call segmented_write_std didn't propagate access correctly. As such, during userspace induced exception, the guest can incorrectly assume that the exception happened in the kernel and panic. (bsc#1097108).
<summary>Security update for the Linux Kernel (Live Patch 1 for SLE 15)</summary>
openSUSE Build Service is sponsored by