x86_64, UEFI
Intel Core i7-4790 (-HT-MCP-), NVIDIA GTX970

$ uname -r
4.14.116-1.mga6
nvidia driver 390.87 built and installed during the reboot.  Same for virtualbox.
Desktop behaving normally.  Ran the usual stress tests successfully.
bluetooth connected immediately to audio device.
Launched a virtualbox client - no problems.

CC: (none) => tarazed25

Aorus X5 laptop - x86_64, UEFI
Intel Core i7-5700HQ (-HT-MCP-), NVIDIA GTX965M * 2

Installed kernel-linus, devel packages first.  nvidia 410.78 built in session.
It appears that the grub2 menu needs to be updated by the user with this kernel - using 'drakboot --boot' here.
Rebooted to 4.14.116-1.mga6 on Mate desktop.  Everything looks OK.  NFS shares mounted with 'sudo mount -a'.  Networking has to be enabled after login by giving the root password twice.  This is nothing new - possibly something to do with bluetooth. Laptop suspends and resumes when lid is closed and opened.
Ran stress tests, teapot, glxspheres64, glmark2 - nothing unusual to report.

Intel Core i9-7900X (-HT-MCP-), UEFI
NVIDIA GP102 [GeForce GTX 1080 Ti]

Installed the linus kernel.  Noted that nvidia304 and nvidia340 were being installed as well as nvidia390.
$ drakboot --boot
Rebooted smoothly with 4.14.116-1.mga6.
NFS shares mounted before the double request for the root password.
The desktop looks functional but bluetooth does not work.  It is running; no status errors.  From dmesg:
[   40.767336] Bluetooth: RFCOMM TTY layer initialized
[   40.767340] Bluetooth: RFCOMM socket layer initialized
[   40.767343] Bluetooth: RFCOMM ver 1.11
[   59.811583] Bluetooth: hci0 command 0x0c01 tx timeout

$ bluetoothctl
[NEW] Controller 00:02:5B:00:A5:A5 canopus [default]
Agent registered
[bluetooth]# power on
Changing power on succeeded
[bluetooth]# discoverable on
Changing discoverable on succeeded
[bluetooth]# scan on
Discovery started
[CHG] Controller 00:02:5B:00:A5:A5 Discovering: yes
[bluetooth]# list
Controller 00:02:5B:00:A5:A5 canopus [default]
[bluetooth]# 

After a systemd restart:
[CHG] Controller 00:02:5B:00:A5:A5 Name: canopus
[CHG] Controller 00:02:5B:00:A5:A5 Alias: BlueZ 5.45
[CHG] Controller 00:02:5B:00:A5:A5 Class: 0x1c0104
[CHG] Controller 00:02:5B:00:A5:A5 Powered: yes
[CHG] Controller 00:02:5B:00:A5:A5 Alias: canopus

Not working.  Fared no better with blueman-assistant or bluedevil-wizard.
Note that there have been continuing problems with bluetooth on this machine so  this is probably not kernel specific - possibly some basic configuration issue.

Apologies for that spiel in comment 3.  It really belongs in a bug report.

Advisory, added to svn:

type: security
subject: Updated kernel-linus packages fixes security vulnerabilities
CVE:
 - CVE-2018-1000026
 - CVE-2019-3882
 - CVE-2019-7308
 - CVE-2019-9213
 - CVE-2019-11486
 - CVE-2019-11599
src:
  6:
   core:
     - kernel-linus-4.14.116-1.mga6
description: |
  This kernel-linus update is based on the upstream 4.14.116 and fixes
  atleast the following security issues:

  Linux Linux kernel version at least v4.8 onwards, probably well before
  contains a Insufficient input validation vulnerability in bnx2x network
  card driver that can result in DoS: Network card firmware assertion takes
  card off-line. This attack appear to be exploitable via An attacker on a
  must pass a very large, specially crafted packet to the bnx2x card.
  This can be done from an untrusted guest VM (CVE-2018-1000026)

  A flaw was found in the Linux kernel's vfio interface implementation that
  permits violation of the user's locked memory limit. If a device is bound
  to a vfio driver, such as vfio-pci, and the local attacker is
  administratively granted ownership of the device, it may cause a system
  memory exhaustion and thus a denial of service (DoS) (CVE-2019-3882).

  kernel/bpf/verifier.c in the Linux kernel before 4.20.6 performs undesirable
  out-of-bounds speculation on pointer arithmetic in various cases, including
  cases of different branches with different state or limits to sanitize,
  leading to side-channel attacks (CVE-2019-7308).

  In the Linux kernel before 4.20.14, expand_downwards in mm/mmap.c lacks
  a check for the mmap minimum address, which makes it easier for attackers
  to exploit kernel NULL pointer dereferences on non-SMAP platforms. This is
  related to a capability check for the wrong task (CVE-2019-9213).

  The Siemens R3964 line discipline driver in drivers/tty/n_r3964.c in the
  Linux kernel before 5.0.8 has multiple race conditions (CVE-2019-11486).

  The coredump implementation in the Linux kernel before 5.0.10 does not use
  locking or other mechanisms to prevent vma layout or vma flags changes while
  it runs, which allows local users to obtain sensitive information, cause a
  denial of service, or possibly have unspecified other impact by triggering
  a race condition with mmget_not_zero or get_task_mm calls (CVE-2019-11599).

  It also fixes signal handling issues causing powertop to crash and some
  tracing tools to fail on execve tests.

  For other uptstream fixes in this update, see the referenced changelogs.
references:
 - https://bugs.mageia.org/show_bug.cgi?id=24775
 - https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.14.101
 - https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.14.102
 - https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.14.103
 - https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.14.104
 - https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.14.105
 - https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.14.106
 - https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.14.107
 - https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.14.108
 - https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.14.109
 - https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.14.110
 - https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.14.111
 - https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.14.112
 - https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.14.113
 - https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.14.114
 - https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.14.115
 - https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.14.116

Keywords: (none) => advisory

updating to 4.14.119 to include the Intel MDS Security issue that went public a few hours ago...


SRPMS:
kernel-linus-4.14.119-1.mga6.src.rpm


i586:
kernel-linus-4.14.119-1.mga6-1-1.mga6.i586.rpm
kernel-linus-devel-4.14.119-1.mga6-1-1.mga6.i586.rpm
kernel-linus-devel-latest-4.14.119-1.mga6.i586.rpm
kernel-linus-doc-4.14.119-1.mga6.noarch.rpm
kernel-linus-latest-4.14.119-1.mga6.i586.rpm
kernel-linus-source-4.14.119-1.mga6-1-1.mga6.noarch.rpm
kernel-linus-source-latest-4.14.119-1.mga6.noarch.rpm


x86_64:
kernel-linus-4.14.119-1.mga6-1-1.mga6.x86_64.rpm
kernel-linus-devel-4.14.119-1.mga6-1-1.mga6.x86_64.rpm
kernel-linus-devel-latest-4.14.119-1.mga6.x86_64.rpm
kernel-linus-doc-4.14.119-1.mga6.noarch.rpm
kernel-linus-latest-4.14.119-1.mga6.x86_64.rpm
kernel-linus-source-4.14.119-1.mga6-1-1.mga6.noarch.rpm
kernel-linus-source-latest-4.14.119-1.mga6.noarch.rpm

Summary: Update request: kernel-linus-4.14.116-1.mga6 => Update request: kernel-linus-4.14.119-1.mga6
Severity: normal => critical
Priority: Normal => High

Addendum to Advisory:

  This update adds the kernel side mitigations for the Microarchitectural
  Data Sampling (MDS, also called ZombieLoad attack) vulnerabilities in
  Intel processors that can allow attackers to retrieve data being processed
  inside a CPU. To complete the mitigations new microcode is also needed,
  either by installing the microcode-0.20190514-1.mga6 package, or get an
  updated bios / uefi firmware from the motherboard vendor.

  The fixed / mitigated issues are:

  Modern Intel microprocessors implement hardware-level micro-optimizations
  to improve the performance of writing data back to CPU caches. The write
  operation is split into STA (STore Address) and STD (STore Data)
  sub-operations. These sub-operations allow the processor to hand-off
  address generation logic into these sub-operations for optimized writes.
  Both of these sub-operations write to a shared distributed processor
  structure called the 'processor store buffer'. As a result, an
  unprivileged attacker could use this flaw to read private data resident
  within the CPU's processor store buffer. (CVE-2018-12126)

  Microprocessors use a ‘load port’ subcomponent to perform load operations
  from memory or IO. During a load operation, the load port receives data
  from the memory or IO subsystem and then provides the data to the CPU
  registers and operations in the CPU’s pipelines. Stale load operations
  results are stored in the 'load port' table until overwritten by newer
  operations. Certain load-port operations triggered by an attacker can be
  used to reveal data about previous stale requests leaking data back to the
  attacker via a timing side-channel. (CVE-2018-12127)

  A flaw was found in the implementation of the "fill buffer", a mechanism
  used by modern CPUs when a cache-miss is made on L1 CPU cache. If an
  attacker can generate a load operation that would create a page fault,
  the execution will continue speculatively with incorrect data from the
  fill buffer while the data is fetched from higher level caches. This
  response time can be measured to infer data in the fill buffer.
  (CVE-2018-12130)

  Uncacheable memory on some microprocessors utilizing speculative execution
  may allow an authenticated user to potentially enable information disclosure
  via a side channel with local access. (CVE-2019-11091)

references:
- https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/mds.html

Intel Core i7-4790 (-HT-MCP-) x86_64
NVIDIA GM204 [GeForce GTX 970] : nvidia 390.87

Everything running smoothly, bluetooth out of the box.
NFS shares reconnected on client machine.

Intel Core i9-7900X (-HT-MCP-) 
NVIDIA GP102 [GeForce GTX 1080 Ti] - nvidia 390.87

My usual set of tests worked fine.
Leaving this running to download the RC Live isos.

Enough tests, flushing it out

Whiteboard: (none) => MGA6-64-OK
Keywords: (none) => validated_update
CC: (none) => sysadmin-bugs

Enough tests, flushing it out

An update for this issue has been pushed to the Mageia Updates repository.

https://advisories.mageia.org/MGASA-2019-0172.html

Status: NEW => RESOLVED
Resolution: (none) => FIXED