VirtualBox 6.1.22 arrives a few days after version 6.1.20 to solve some problems

Oracle Released Corrective Release of VirtualBox 6.1.22 which was sent as a patch that includes 5 fixes and is that days before Oracle had published VirtualBox 6.1.20, but after that and detected the faults, this corrective version was released.

For the 6.1.20 part the changelog does not explicitly address the 20 vulnerabilities that Oracle reported separately but without details. Only the three most dangerous problems are known to have severity levels 8.1, 8.2, and 8.4 (probably allowing access to the host system from a virtual machine), and one of the problems allows a remote attack by manipulating the RDP protocol.

On the part of the main changes that were introduced highlights the support for Linux kernels 5.11 and 5.12 for Linux hosts and guests. In addition to the additions for guest systems using Linux 4.10+ kernels through 16110, the maximum MTU size for host-only mode network adapters has been increased.

Guest plugins fix an issue with building the vboxvideo module for Linux 5.10.x kernels, plus guest additions provide support for compiling kernel modules on RHEL 8.4-beta and CentOS Stream distributions.

In VBoxManage, it is allowed to use the “modifyvm” command to change the attachment of a network adapter to a saved virtual machine.

Components for integration with OCI (Oracle Cloud Infrastructure) added the ability to use cloud-init to export to OCI and to instantiate environments in OCI.

In the GUI, the problem of leaving the log Logs / VBoxUI.log when performing the operation to delete all files (“Delete all files”) is solved.

What’s more, fixed a performance issue in Virtual Machine Manager (VMM), issues with handling guest systems with the Hyper-V hypervisor were resolved, and a bug when using nested virtualization was fixed.

Fixed a SMAP (Supervisor Mode Access Prevention) host crash that occurs in Solaris 11.4 on systems with Intel Haswell and newer processors.

Finally of the fixes that were made in version 6.1.22

  • Also for Linux guests, issues with launching executable files located on mounted shared partitions are resolved.
  • Virtual Machine Manager has improved the startup performance of Windows and Solaris 64-bit guests in Hyper-V mode on Windows 10 host systems.
  • Fixed issues with hangs on Windows Vista 64-bit and Windows Server 2003 when using the Hyper-V hypervisor.
  • Fixed a regressive change in the GUI not allowing to save changes after disabling hotkeys with the Disarm button.
  • Fixed crash when emulating SAS LsiLogic controller.

How to install VirtualBox 6.1.22 in Ubuntu and derivatives?

Before installing, they need to ensure that hardware virtualization is enabled. If they are using an Intel processor, they must enable VT-x or VT-d from their computer’s BIOS.

In the case of Ubuntu and derivatives, we have two methods to install the application or, where appropriate, update to the new version.

The first method is by downloading the “deb” package offered from the official website of the application. The link is this.

The other method is adding the repository to the system. To add the official VirtualBox package repository, they should open a terminal with Ctrl + Alt + T and run the following command:

echo "deb https://download.virtualbox.org/virtualbox/debian $(lsb_release -cs) contrib" | sudo tee /etc/apt/sources.list.d/virtualbox.list

Done this now We must add the public PGP key from the official VirtualBox packages repository to the system.

Otherwise, we will not be able to use the official VirtualBox package repository. To add the public PGP key from the official VirtualBox package repository, run the following command:

wget -q https://www.virtualbox.org/download/oracle_vbox_2016.asc -O- | sudo apt-key add -

We must update the APT package repository with the following command:

sudo apt-get update

Once this is done, now we are going to proceed to install VirtualBox to the system with:

sudo apt install virtualbox-6.2

And ready with it, we can use the new version of VirtualBox in our system.

Add Comment