SUSE-SU-2021:3619-1 Security update for libvirt
Not scored
Published
Check this codebase for SUSE-SU-2021:3619-1 and fix it if it is affected.
What it is: SUSE-SU-2021:3619-1 is a vulnerability in libvirt, published on 5 Nov 2021.
Exploitation: There is no known exploitation of SUSE-SU-2021:3619-1 in the wild and no public exploit code.
Affected product: libvirt. 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/SUSE-SU-2021-3619-1/ (Markdown: https://insights.sbomify.com/SUSE-SU-2021-3619-1/index.md)
This update fixes various bugs in libvirt related to container launching, logging, and configuration handling, without specifying a security vulnerability.
- Exploited in the wild
- Not known
- Login needed
- Not stated
- Attackable
- Not stated
- Victim action needed
- Not stated
- Fix
- Available
What is SUSE-SU-2021:3619-1?
SUSE-SU-2021:3619-1 is a vulnerability in libvirt, published on 5 Nov 2021.
Official description
This update for libvirt fixes the following issues:
- lxc: controller: Fix container launch on cgroup v1. (bsc#1183247)
- supportconfig: Use systemctl command 'is-active' instead of 'is-enabled' when checking if libvirtd is active.
- qemu: Do not report error in the logs when processing monitor IO. (bsc#1190917)
- spec: Fix an issue when package update hangs (bsc#1177902, bsc#1190693)
- spec: Don't add '–timeout' argument to '/etc/sysconfig/libvirtd' when running in traditional mode without socket activation. (bsc#1190695)
- libxl: Improve reporting of 'die_id' in capabilities. (bsc#1190493)
- libxl: Fix driver reload. (bsc#1190420)
- qemu: Set label on virtual host network device when hotplugging. (bsc#1186398)
- supportconfig: When checking for installed hypervisor drivers, use the libvirtr-daemon-driver-<hypervisor> package instead of libvirt-daemon-<hypervisor>. The latter are not required packages for a functioning hypervisor driver.
Which versions are affected by SUSE-SU-2021:3619-1?
Linux distribution packages (3)
libvirt SUSE:Linux Enterprise Micro 5.1 | All versions | 7.1.0-6.8.1 |
libvirt SUSE:Linux Enterprise Module for Basesystem 15 SP3 | All versions | 7.1.0-6.8.1 |
libvirt SUSE:Linux Enterprise Module for Server Applications 15 SP3 | All versions | 7.1.0-6.8.1 |
How do I fix SUSE-SU-2021:3619-1?
Apply the vendor's patch.
Is SUSE-SU-2021:3619-1 being exploited?
There is no known exploitation of SUSE-SU-2021:3619-1 in the wild and no public exploit code.