Bug 25687 - Update request: kernel-linus-5.3.11-1.mga7
Summary: Update request: kernel-linus-5.3.11-1.mga7
Alias: None
Product: Mageia
Classification: Unclassified
Component: Security (show other bugs)
Version: 7
Hardware: All Linux
Priority: Normal critical
Target Milestone: ---
Assignee: QA Team
QA Contact: Sec team
Whiteboard: MGA7-64-OK
Keywords: advisory, validated_update
Depends on:
Reported: 2019-11-13 12:01 CET by Thomas Backlund
Modified: 2019-11-19 22:19 CET (History)
2 users (show)

See Also:
Source RPM: kernel-linus
Status comment:


Description Thomas Backlund 2019-11-13 12:01:21 CET
smashing the latest ZombieLoad series cpu security issues, intel gpu security issues and other fixes...



Comment 1 Len Lawrence 2019-11-14 19:37:56 CET
Kernel linus and desktop updates on four machines after the new microcode.
Just a quick summary of installation and reboot.

CPU: Quad Core Intel Core i7-4790 (-MT MCP-)
NVIDIA GM204 [GeForce GTX 970] driver: nvidia v: 430.50
Linus kernel failed to reach desktop after building various modules.
Moved to a console and ran XFdrake - apparently OK but reboot simply hung.

Legacy boot:
Alienware X51
Quad Core: Intel Core i7-2600 type: MT MCP speed: 1596 MHz
Intel 2nd Generation Core Processor Family Integrated Graphics 
NVIDIA GF114 [GeForce GTX 555] driver: nvidia v: 390.129
Linus kernel failed to reach desktop in much the same way as before.  When the warning about the graphics module mismatch comes up hitting return leads to an apparent freeze (no virtual consoles) but it is possible to reboot with the three finger salute.

CPU: 10-Core: Intel Core i9-7900X type: MT MCP speed: 1200 MHz
NVIDIA GP102 [GeForce GTX 1080 Ti] driver: nvidia v: 430.50
Failed to reboot after installation.  Came up with a complaint about conflicting drivers - reboot needed but as with the desktop kernel on this machine it had to be a cold reboot.  Ran through this loop several times before a final successful reboot to the desktop but under the nouveau driver.  The nvidia driver was rebuilt and installed but seems to be unusable.  Running out of time for expeeiments.

Asus X5 laptop
Quad Core Intel Core i7-5700HQ (-MT MCP-) 
GeForce GTX 965M/PCIe/SSE2 v: 4.6.0 NVIDIA 430.50
Using the older microcode.
Installed the linus kernel and hit the conflicting drivers problem again.  After a couple of iterations tried the nomodeset kernel option and succeeded in booting to the desktop with the nvidia 430.50 driver in place.

That is the story so far.

CC: (none) => tarazed25

Comment 2 Thomas Backlund 2019-11-19 21:36:42 CET
Advisory, added to svn:

type: security
subject: Updated kernel-linus packages fix security vulnerabilities
 - CVE-2019-0155
 - CVE-2019-1125
 - CVE-2019-10207
 - CVE-2019-11135
 - CVE-2018-12207
 - CVE-2019-14814
 - CVE-2019-14815
 - CVE-2019-14816
 - CVE-2019-14821
 - CVE-2019-14835
 - CVE-2019-16714
 - CVE-2019-17666
     - kernel-linus-5.3.11-1.mga7
description: |
  This kernel-linus update is based on the upstream 5.3.13 and fixes atleast
  the following security issues:

  Insufficient access control in a subsystem for Intel (R) processor graphics
  may allow an authenticated user to potentially enable escalation of
  privilege via local access (CVE-2019-0155).

  A Spectre SWAPGS gadget was found in the Linux kernel's implementation of
  system interrupts. An attacker with local access could use this information
  to reveal private data through a Spectre like side channel (CVE-2019-1125).

  A flaw was found in the Linux kernel’s Bluetooth implementation of UART.
  An attacker with local access and write permissions to the Bluetooth
  hardware could use this flaw to issue a specially crafted ioctl function
  call and cause the system to crash (CVE-2019-10207).

  TSX Asynchronous Abort condition on some CPUs utilizing speculative
  execution may allow an authenticated user to potentially enable
  information disclosure via a side channel with local access

  Improper invalidation for page table updates by a virtual guest operating
  system for multiple Intel(R) Processors may allow an authenticated user to
  potentially enable denial of service of the host system via local access

  For proper mitigations and fixes for theese issues, a microcode update is
  also needed, either with a bios/uefi update from your hardware vendor or
  by installing the microcode-0.20191112-1.mga7.nonfree update (mga#25688).

  There is heap-based buffer overflow in the marvell wifi chip driver that
  allows local users to cause a denial of service(system crash) or possibly
  execute arbitrary code (CVE-2019-14814, CVE-2019-14815, CVE-2019-14816).

  An out-of-bounds access issue was found in the way Linux kernel's KVM
  hypervisor implements the Coalesced MMIO write operation. It operates on
  an MMIO ring buffer 'struct kvm_coalesced_mmio' object, wherein write
  indices 'ring->first' and 'ring->last' value could be supplied by a host
  user-space process. An unprivileged host user or process with access to
  '/dev/kvm' device could use this flaw to crash the host kernel, resulting
  in a denial of service or potentially escalating privileges on the system

  A buffer overflow flaw was found in the way Linux kernel's vhost
  functionality that translates virtqueue buffers to IOVs, logged the buffer
  descriptors during migration. A privileged guest user able to pass
  descriptors with invalid length to the host when migration is underway,
  could use this flaw to increase their privileges on the host

  In the Linux kernel before 5.2.14, rds6_inc_info_copy in net/rds/recv.c
  allows attackers to obtain sensitive information from kernel stack memory
  because tos and flags fields are not initialized (CVE-2019-16714)

  rtl_p2p_noa_ie in drivers/net/wireless/realtek/rtlwifi/ps.c in the Linux
  kernel through 5.3.6 lacks a certain upper-bound check, leading to a
  buffer overflow (CVE-2019-17666)

  For other upstream fixes in this update, see the referenced changelogs.
 - https://bugs.mageia.org/show_bug.cgi?id=25687
 - https://bugs.mageia.org/show_bug.cgi?id=25688
 - https://kernelnewbies.org/Linux_5.2
 - https://kernelnewbies.org/Linux_5.3
 - https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.3.1
 - https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.3.2
 - https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.3.3
 - https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.3.4
 - https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.3.5
 - https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.3.6
 - https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.3.7
 - https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.3.8
 - https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.3.9
 - https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.3.10
 - https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.3.11

CC: (none) => sysadmin-bugs
Keywords: (none) => advisory, validated_update
Whiteboard: (none) => MGA7-64-OK

Comment 3 Mageia Robot 2019-11-19 22:19:11 CET
An update for this issue has been pushed to the Mageia Updates repository.


Resolution: (none) => FIXED

Note You need to log in before you can comment on or make changes to this bug.