Bug 29385

Advisory, added to svn:

type: security
subject: Updated kernel-linus packages fix security vulnerabilities
CVE:
 - CVE-2021-3653
 - CVE-2021-3656
 - CVE-2021-38205
src:
  8:
   core:
     - kernel-linus-5.10.60-1.mga8
description: |
  This kernel-linus update is based on upstream 5.10.60 and fixes atleast
  the following security issues:

  A missing validation of the "int_ctl" VMCB field allows a malicious L1
  guest to enable AVIC support (Advanced Virtual Interrupt Controller)
  for the L2 guest. The L2 guest is able to write to a limited but still
  relatively large subset of the host physical memory, resulting in a
  crash of the entire system, leak of sensitive data or potential
  guest-to-host escape (CVE-2021-3653).

  A missing validation of the the "virt_ext" VMCB field and allows a
  malicious L1 guest to disable both VMLOAD/VMSAVE intercepts and VLS
  (Virtual VMLOAD/VMSAVE) for the L2 guest. Under these circumstances,
  the L2 guest is able to run VMLOAD/VMSAVE unintercepted, and thus
  read/write portions of the host physical memory, resulting in a
  crash of the entire system, leak of sensitive data or potential
  guest-to-host escape (CVE-2021-3656).

  drivers/net/ethernet/xilinx/xilinx_emaclite.c in the Linux kernel before
  5.13.3 makes it easier for attackers to defeat an ASLR protection
  mechanism because it prints a kernel pointer ().

  For other upstream fixes, see the referenced changelogs.
references:
 - https://bugs.mageia.org/show_bug.cgi?id=29385
 - https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.10.57
 - https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.10.58
 - https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.10.59
 - https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.10.60

Keywords: (none) => advisory

Quad Core Intel Core i7-4790
Kernel: 5.10.60-1.mga8 x86_64
NVIDIA GM204 [GeForce GTX 970]

Linus kernel installed without problems.  Rebuilt nvidia-current and virtualbox driver.
NFS shares and NAS drive available at login.  No problems noted but bluetooth took a little time to set up.  This time a device search found the portable audio device and managed to pair.
Leaving this running for a few days.

CC: (none) => tarazed25

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

https://advisories.mageia.org/MGASA-2021-0410.html

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