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

> Bug fixes for KVM virtualization issues in AlmaLinux, addressing PCI passthrough errors and VM creation failures.

- **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:** 17 Dec 2019

## What is ALBA-2019:4274?

ALBA-2019:4274 is a vulnerability in libiscsi, published on 17 Dec 2019. 

### Official description

Bug Fix(es):

* RHEL8.1 Snapshot3 - Passthrough PCI card goes into error state if used in domain (kvm) (BZ#1764829)

* [HPE 8.1 BUG] Icelake: KVM missing .pconfig (BZ#1775133)

* Failed to create a VM via virt-manager or web console in RHEL8.1 snapshot-2.1 (BZ#1775134)

* [Intel 8.2 Bug] Icelake-Server host, mode=host-model: "can't apply global Icelake-Server-x86_64-cpu.pconfig=off: Property '.pconfig' not found" (BZ#1775137)

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `libiscsi` | AlmaLinux:8 | All versions | 1.18.0-8.module_el8.3.0+2048+e7a0a3ea |
| `libiscsi` | AlmaLinux:8 | All versions | 1.18.0-8.module_el8.5.0+2608+72063365 |
| `libiscsi` | AlmaLinux:8 | All versions | 1.18.0-8.module_el8.6.0+2880+7d9e3703 |
| `libiscsi-devel` | AlmaLinux:8 | All versions | 1.18.0-8.module_el8.3.0+2048+e7a0a3ea |
| `libiscsi-devel` | AlmaLinux:8 | All versions | 1.18.0-8.module_el8.5.0+2608+72063365 |
| `libiscsi-devel` | AlmaLinux:8 | All versions | 1.18.0-8.module_el8.6.0+2880+7d9e3703 |
| `libiscsi-utils` | AlmaLinux:8 | All versions | 1.18.0-8.module_el8.3.0+2048+e7a0a3ea |
| `libiscsi-utils` | AlmaLinux:8 | All versions | 1.18.0-8.module_el8.5.0+2608+72063365 |
| `libiscsi-utils` | AlmaLinux:8 | All versions | 1.18.0-8.module_el8.6.0+2880+7d9e3703 |
| `netcf` | AlmaLinux:8 | All versions | 0.2.8-12.module_el8.3.0+2048+e7a0a3ea |
| `netcf` | AlmaLinux:8 | All versions | 0.2.8-12.module_el8.5.0+2608+72063365 |
| `netcf` | AlmaLinux:8 | All versions | 0.2.8-12.module_el8.6.0+2880+7d9e3703 |
| `netcf-devel` | AlmaLinux:8 | All versions | 0.2.8-12.module_el8.3.0+2048+e7a0a3ea |
| `netcf-devel` | AlmaLinux:8 | All versions | 0.2.8-12.module_el8.5.0+2608+72063365 |
| `netcf-devel` | AlmaLinux:8 | All versions | 0.2.8-12.module_el8.6.0+2880+7d9e3703 |
| `netcf-libs` | AlmaLinux:8 | All versions | 0.2.8-12.module_el8.3.0+2048+e7a0a3ea |
| `netcf-libs` | AlmaLinux:8 | All versions | 0.2.8-12.module_el8.5.0+2608+72063365 |
| `netcf-libs` | AlmaLinux:8 | All versions | 0.2.8-12.module_el8.6.0+2880+7d9e3703 |
| `sgabios` | AlmaLinux:8 | All versions | 1:0.20170427git-3.module_el8.3.0+2048+e7a0a3ea |
| `sgabios` | AlmaLinux:8 | All versions | 1:0.20170427git-3.module_el8.5.0+2608+72063365 |
| `sgabios-bin` | AlmaLinux:8 | All versions | 1:0.20170427git-3.module_el8.5.0+2608+72063365 |

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

Apply the vendor's patch.

## Is ALBA-2019:4274 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: ALBA-2019:4274 is a vulnerability in libiscsi, published on 17 Dec 2019. 
Exploitation: There is no known exploitation of ALBA-2019:4274 in the wild and no public exploit code.

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

## Sources

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

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