# ALBA-2019:2715: virt:rhel bug fix update

> A bug in QEMU-KVM causes a core dump when hotplugging deleted disks with iothread parameters, leading to denial of service for virtual machines.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 10 Sep 2019

## What is ALBA-2019:2715?

ALBA-2019:2715 is a denial of service vulnerability in sgabios, published on 10 Sep 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Bug Fix(es):

* qemu-kvm core dumped after hotplug the deleted disk with iothread parameter (BZ#1718992)

* Detached device when trying to upgrade USB device firmware when in doing USB Passthrough via QEMU (BZ#1719228)

## Which versions are affected by ALBA-2019:2715?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `sgabios` | AlmaLinux:8 | All versions | 1:0.20170427git-3.module_el8.6.0+2880+7d9e3703 |
| `sgabios-bin` | AlmaLinux:8 | All versions | 1:0.20170427git-3.module_el8.6.0+2880+7d9e3703 |

## How do I fix ALBA-2019:2715?

Apply the vendor's patch.

## Is ALBA-2019:2715 being exploited?

There is no known exploitation of ALBA-2019:2715 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for ALBA-2019:2715 and fix it if it is affected.

What it is: ALBA-2019:2715 is a denial of service vulnerability in sgabios, published on 10 Sep 2019. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of ALBA-2019:2715 in the wild and no public exploit code.

Affected product: sgabios. 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/ALBA-2019-2715/ (Markdown: https://insights.sbomify.com/ALBA-2019-2715/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/ALBA-2019:2715

---
From sbomify Insights: https://insights.sbomify.com/ALBA-2019-2715/
Summaries are generated and may contain mistakes; the official description above is the record.