# openSUSE-SU-2023:0213-1: Security update for virtualbox

> This update fixes various bugs in VirtualBox, including crashes and log flooding, improving stability for virtual machine users.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Not stated
- **Victim action needed:** Not stated
- **Fix available:** Yes
- **Published:** 6 Aug 2023

## What is openSUSE-SU-2023:0213-1?

openSUSE-SU-2023:0213-1 is a vulnerability in virtualbox, published on 6 Aug 2023. 

### Official description

This update for virtualbox fixes the following issues:

VirtualBox 7.0.10 (released July 18 2023)

This is a maintenance release. The following items were fixed and/or added:

- OCI: Introduced general improvements
- VMM: Fixed a bug while walking page tables while executing nested VMs causing flooding of the release log as a consequence (Intel hosts only, bug #21551)
- GUI: Added general improvements
- TPM: Fixed a crash when a VM has a TPM version 1.2 configured (bug #21622)
- 3D: Initial support for OpenGL 4.1
- 3D: Fixed various graphics issues with Windows 11 guests (bugs #21136, #21515)
- Guest Control/VBoxManage: Fixed parameter '--ignore-orphaned-processes'
- Guest Control/VBoxManage: Fixed behavior of how handling argument 0 for a started guest process works: One can now explicitly specify it with the newly added option '--arg0'. This will effectively restore the behavior of former VirtualBox versions
- Audio: Also use the PulseAudio backend when pipewire-pulse is running instead of falling back to ALSA (bug #21575)
- NAT: Adjusted UDP proxy timeout from 18-21 to 21-24 range to respect intended 20 second timeout (bug #21560)
- Linux Host: Added initial support for Indirect Branch Tracking (bug #21435)
- Linux Host: Added initial support for kernel 6.5 (NOTE: Guest Additions do not support kernel 6.5 yet)
- Linux Host and Guest: Improved condition check when kernel modules need to be signed
- Linux Host and Guest: Added initial support for RHEL 8.8 (bug #21692), 8.9 (bug #21690) and 9.3 (bugs #21598 and #21671) kernels
- Linux Guest Additions: Fixed issue when kernel modules were rebuilt on each boot when guest system has no X11 installed
- Linux Guest Additions: Added initial support for kernel 6.4
- Linux Guest Additions: Fixed issue when vboxvideo module reloading caused kernel panic in some guests (bug #21740)
- Linux Guest Additions: Introduced general improvements in the installer area
- Windows Guest Additions: Introduced general improvements in graphics drivers area 
- Fix issue with kernel on newer CPU (boo#1212209)
 
- Turn build of VBoxSDL back on. This update addresses boo#1211941.
- Detect vboxpython module with python 3.11
- Fix Vagrant/virtualbox startup problems boo#1209727

## Which versions are affected by openSUSE-SU-2023:0213-1?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `virtualbox` | openSUSE:Leap 15.5 | All versions | 7.0.10-lp155.2.5.1 |
| `virtualbox-kmp` | openSUSE:Leap 15.5 | All versions | 7.0.10-lp155.2.5.1 |

## How do I fix openSUSE-SU-2023:0213-1?

Upgrade to a fixed version.

## Is openSUSE-SU-2023:0213-1 being exploited?

There is no known exploitation of openSUSE-SU-2023:0213-1 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for openSUSE-SU-2023:0213-1 and fix it if it is affected.

What it is: openSUSE-SU-2023:0213-1 is a vulnerability in virtualbox, published on 6 Aug 2023. 
Exploitation: There is no known exploitation of openSUSE-SU-2023:0213-1 in the wild and no public exploit code.

Affected product: virtualbox. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/openSUSE-SU-2023-0213-1/ (Markdown: https://insights.sbomify.com/openSUSE-SU-2023-0213-1/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/openSUSE-SU-2023:0213-1

---
From sbomify Insights: https://insights.sbomify.com/openSUSE-SU-2023-0213-1/
Summaries are generated and may contain mistakes; the official description above is the record.